Dear Martin,
Am Dienstag, den 03.10.2017, 08:07 -0600 schrieb Martin Roth:
I'd say that it doesn't make sense to require that coreboot builds with anything other than the coreboot toolchain. Additionally, It isn't reasonable to introduce a new requirement this close to the release.
Having the code base compatible with future toolchains is quite important and convenient in my opinion.
Especially for bisecting an issue, people don’t rebuild the toolchain in each step. In practice, people also don’t rebuild the toolchain each time, as it takes so much time. And going back, and being hold up, because there are build problems with the new toolchain is very inconvenient.
Also, I believe the build system does not warn about, if you use a newer toolchain.
The good side is, that most warnings and errors of newer toolchains actually point out real problems – most of them don’t affect anything though –, so fixing those would be a good thing.
Thanks,
Paul
2017-10-06 9:43 GMT+02:00 Paul Menzel paulepanter@users.sourceforge.net:
Having the code base compatible with future toolchains is quite important and convenient in my opinion.
That's a great argument to switch out the toolchain 4 months before a release. Which means 3.5 months ago.
Especially for bisecting an issue, people don’t rebuild the toolchain in each step.
Which means that no matter what we do to crossgcc, there's no reproducibility. That's not a good argument for doing something or anything at all.
The good side is, that most warnings and errors of newer toolchains actually point out real problems – most of them don’t affect anything though –, so fixing those would be a good thing.
Fixing real issues? Yes, please. Swapping out the entire code optimizer phase, potentially introducing regressions through no code change at all in coreboot itself? Not at this time.
Patrick
* Paul Menzel paulepanter@users.sourceforge.net [171006 09:43]:
Dear Martin,
Am Dienstag, den 03.10.2017, 08:07 -0600 schrieb Martin Roth:
I'd say that it doesn't make sense to require that coreboot builds with anything other than the coreboot toolchain. Additionally, It isn't reasonable to introduce a new requirement this close to the release.
Having the code base compatible with future toolchains is quite important and convenient in my opinion.
And if you wish to lead this effort, patches are very welcome.
Stefan