Martin Roth has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/38907 )
Change subject: crossgcc: Upgrade IASL to version 20200214 ......................................................................
Patch Set 3:
Patch Set 3:
Patch Set 2: Code-Review-2
No. A version bump (to 20200110) was submitted literally earlier this month: https://review.coreboot.org/c/coreboot/+/38347 If this has introduced bugs or broken the tree, feel free to remove my score.
That earlier version bump was delayed for months (before 20200110 there were a few more versions we skipped) because we had to fix up our tree first.
Since you seem to feel strongly about this: what's the cut-off we should follow in your opinion? Monthly updates?
And why?
Personally, I'm in favor of quarterly updates for most of the toolchain unless there's an issue that requires an update sooner than that.
I think we should do GCC updates every 6 months, preferably immediately after a release so that there's plenty of time to find and fix any issues created before the next release.
I've got a builder set up to do daily testing with the updated IASL. I could expand that to do the full toolchain update on a daily basis.
And it looks like we're failing to build GDB with the new jenkins image. I'll work to fix that this weekend and probably need to update all the builders to a new coreboot-sdk docker image again. I hadn't been testing building the toolchain on the new docker image, so it seems like I need to add that. I didn't think it was needed because when the image is created, the first thing it does is build the toolchain, but it doesn't build GDB. :(