[Bug target/96939] LTO vs. different arm arch options

2020-09-10 Thread cvs-commit at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96939 --- Comment #9 from CVS Commits --- The master branch has been updated by Jakub Jelinek : https://gcc.gnu.org/g:57e113cf7c94a682c29566cb3e0e85955904fd35 commit r11-3104-g57e113cf7c94a682c29566cb3e0e85955904fd35 Author: Jakub Jelinek Date: Th

[Bug target/96939] LTO vs. different arm arch options

2020-09-07 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96939 --- Comment #8 from Jakub Jelinek --- So I think this bug has been introduced with https://gcc.gnu.org/legacy-ml/gcc-patches/2016-12/msg01390.html I think the right change is: --- gcc/config/arm/arm.c.jj 2020-07-30 15:04:38.136293101 +0200 ++

[Bug target/96939] LTO vs. different arm arch options

2020-09-04 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96939 --- Comment #7 from Jakub Jelinek --- AFAIK targetm.override_options_after_change is called at the end of switching optimization (but not target) options. So, that is a good hook to e.g. adjust something cached from those non-target Optimization

[Bug target/96939] LTO vs. different arm arch options

2020-09-04 Thread rearnsha at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96939 --- Comment #6 from Richard Earnshaw --- (In reply to Jakub Jelinek from comment #4) > Doesn't seem to be related to me, in the other PR everything is compiled > with one set of options and no target attribute is involved either. No, that's a co

[Bug target/96939] LTO vs. different arm arch options

2020-09-04 Thread rearnsha at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96939 --- Comment #5 from Richard Earnshaw --- I batted my head against this when reworking the command line options stuff a couple of years back, but the documentation on how the different hooks should interact (especially for LTO and streaming) is, q

[Bug target/96939] LTO vs. different arm arch options

2020-09-04 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96939 --- Comment #4 from Jakub Jelinek --- Doesn't seem to be related to me, in the other PR everything is compiled with one set of options and no target attribute is involved either.

[Bug target/96939] LTO vs. different arm arch options

2020-09-04 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96939 --- Comment #3 from Andrew Pinski --- I think this is related to or a dup of bug 96882.

[Bug target/96939] LTO vs. different arm arch options

2020-09-04 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96939 Jakub Jelinek changed: What|Removed |Added Ever confirmed|0 |1 Last reconfirmed|

[Bug target/96939] LTO vs. different arm arch options

2020-09-04 Thread law at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96939 Jeffrey A. Law changed: What|Removed |Added CC||law at redhat dot com --- Comment #1 fr