https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92860
--- Comment #65 from David Binderman <dcb314 at hotmail dot com> --- (In reply to David Binderman from comment #63) > OR: I do a fishing trip for revisions some unknown time before > 2020-06-11 (the known bad date), to find a known good date, then > run git bisect from there. > > In furtherance of option 2 and given that Jun 2020 is long enough > ago that the git rev-list will have expired (it is only valid for 90 days), > am I correct in thinking that something like > > git rev-list -n 1 --first-parent --before="2020-01-01" master > > will give me a git hash of a revision of the first day of year 2020 > and so > > git checkout `that git hash` > > will get me to that date, so I can run a build ? Yes, those git commands seem to successfully get me backwards and forwards on the git timeline, but I am struggling to get anything to build. I've tried: 2020-04-11 : f883c46b4877f637e0fa5025b4d6b5c9040ec566 good ? cyclades problems 2020-05-11 : dbeaa7ab81a37acadc9af6e7990332604252de20 failed to build 2020-06-11 : 419c355c7a871513e1065b7cec32dd456eb4a0e5 failed to build 2020-07-11 : c19f95fb1b8f15090eb1d1682e86de425fbd3c78 failed to build 2020-08-11 : 1118a3ff9d3ad6a64bba25dc01e7703325e23d92 failed to build 2020-09-11 : 8d3767c30240c901a493d82d9d20f306b2f0152d failed to build where column 1 is a date, column 3 is the git hash and column 4 indicates that I could only build one of the versions I tried, from Apr 2021, and that was questionable, because of problems with cyclades header files. I had to use make -k in the end. Most of the rest stopped with this error message: /usr/include/stdio.h:183:3: error: wrong number of arguments specified for ‘malloc’ attribute /usr/include/stdio.h:183:3: error: wrong number of arguments specified for ‘malloc’ attribute /usr/include/stdio.h:183:3: error: wrong number of arguments specified for ‘malloc’ attribute /usr/include/stdio.h:195:4: error: wrong number of arguments specified for ‘malloc’ attribute I don't know how to fix that. Given the copious activity and lack of progress on this bug report, I would be happy for it to be closed down as "cannot reproduce".
