[Bug middle-end/64242] Longjmp expansion incorrect

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64242 --- Comment #17 from Jeffrey A. Law --- Or just emit a blockage insn to avoid the undesirable code motion.

[Bug middle-end/24639] [meta-bug] bug to track all Wuninitialized issues

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24639 Bug 24639 depends on bug 79768, which changed state. Bug 79768 Summary: `-Wmaybe-uninitialized' false positive with optimisation https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79768 What|Removed |Added

[Bug middle-end/79768] `-Wmaybe-uninitialized' false positive with optimisation

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79768 Jeffrey A. Law changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug rtl-optimization/88179] [9 regression][MIPS] pr84941.c ICE in lra_eliminate_reg_if_possible at lra-eliminations.c:1393 start with r266385

||law at redhat dot com Resolution|--- |FIXED --- Comment #3 from Jeffrey A. Law --- Fixed by Vlad's patch on the trunk.

[Bug middle-end/64242] Longjmp expansion incorrect

||law at redhat dot com Resolution|--- |FIXED --- Comment #6 from Jeffrey A. Law --- Fixed on trunk by Wilco's patch.

[Bug c++/87539] [8 Regression] internal compiler error when compiling project with Os optimization flag

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87539 Jeffrey A. Law changed: What|Removed |Added CC||law at redhat dot com

[Bug target/88207] [9 regression] gcc.target/i386/pr22076.c etc. FAIL

||law at redhat dot com Resolution|--- |FIXED --- Comment #5 from Jeffrey A. Law --- Fixed by Vlad's patch on the trunk.

[Bug middle-end/88246] Abort signal terminated program collect2 - munmap_chunk(): invalid pointer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88246 Jeffrey A. Law changed: What|Removed |Added CC||law at redhat dot com --- Comment #7

[Bug sanitizer/85663] [8/9 Regression] gcc-8.0.1 regression: sanitizer fails to build on mips-unknown-linux-gnu

||2018-11-27 CC||law at redhat dot com Ever confirmed|0 |1

[Bug preprocessor/58397] Please add host_hooks for NetBSD to make precompiled headers work

||law at redhat dot com Resolution|--- |FIXED --- Comment #6 from Jeffrey A. Law --- Fixed on the trunk.

[Bug preprocessor/58370] pre compiled headers failure on NetBSD/sparc64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58370 Bug 58370 depends on bug 58397, which changed state. Bug 58397 Summary: Please add host_hooks for NetBSD to make precompiled headers work https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58397 What|Removed |Added

[Bug tree-optimization/87011] [9 Regression] partially dead memset before strcpy not eliminated

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87011 Jeffrey A. Law changed: What|Removed |Added CC||law at redhat dot com --- Comment #3

[Bug rtl-optimization/87468] [9 Regression] ice "wrong amount of branch edges after conditional jump in bb"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87468 Jeffrey A. Law changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug rtl-optimization/87468] [9 Regression] ice "wrong amount of branch edges after conditional jump in bb"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87468 --- Comment #6 from Jeffrey A. Law --- More correctly, jump threading is duplicating a switch in which there's an outgoing edge marked as EDGE_IGNORE. That duplicate has EDGE_IGNORE set, but isn't in the cleanup queue. Thus it leaks into the

[Bug tree-optimization/52171] memcmp/strcmp/strncmp can be optimized when the result is tested for [in]equality with 0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52171 --- Comment #16 from Jeffrey A. Law --- I think Qing did a fair amount of tuning on this work. If we're not handling a particular case it's likely because it wasn't generally profitable.

[Bug ipa/85103] [8/9 Regression] Performance regressions on SPEC with r257582

||law at redhat dot com

[Bug target/87221] cannot build with -pie

||law at redhat dot com Resolution|--- |FIXED --- Comment #5 from Jeffrey A. Law --- Should be fixed on the trunk.

[Bug middle-end/87813] sprintf pass calling evrp at -O0 and setting global ranges which affect strnlen expansion

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87813 --- Comment #8 from Jeffrey A. Law --- Aldy -- fixing that is a TODO for stage3.

[Bug middle-end/70831] [7/8/9 Regression] FTBFS: Build fails with bootstrap-lto and profiledbootstrap

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70831 Jeffrey A. Law changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug libitm/86293] unused variable left over (used in assert) when building with -g0 -DNDEBUG [-Werror=unused-variable]

||law at redhat dot com Resolution|--- |FIXED --- Comment #1 from Jeffrey A. Law --- Fixed on the trunk.

[Bug middle-end/87813] sprintf pass calling evrp at -O0 and setting global ranges which affect strnlen expansion

||2018-10-30 CC||law at redhat dot com Assignee|unassigned at gcc dot gnu.org |law at redhat dot com Ever confirmed|0 |1 --- Comment #2 from Jeffrey A. Law --- I thought I already had a bug

[Bug rtl-optimization/87664] invariant in loop after optimization

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87664 Jeffrey A. Law changed: What|Removed |Added CC||law at redhat dot com --- Comment #2

[Bug tree-optimization/80155] [7/8/9 regression] Performance regression with code hoisting enabled

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80155 --- Comment #44 from Jeffrey A. Law --- I'd be very hesitant to make the cost model target specific. It goes against core design goals of gimple. Conceptually I believe we should be optimizing as much as possible on gimple and that issues such

[Bug c++/87364] Pretty print of enumerator never prints the id, always falls back to C-style cast output

||law at redhat dot com Resolution|--- |FIXED --- Comment #8 from Jeffrey A. Law --- Patch committed on the trunk

[Bug target/87156] [9 Regression] ICE building libstdc++ for mips64

||law at redhat dot com Resolution|--- |FIXED --- Comment #8 from Jeffrey A. Law --- I committed Jan's patch to the trunk.

[Bug tree-optimization/86829] Missing sin(atan(x)) and cos(atan(x)) optimizations

||law at redhat dot com Resolution|--- |FIXED --- Comment #7 from Jeffrey A. Law --- Fixed by Giuliano's patch I've installed on the trunk.

[Bug middle-end/61409] [6 regression] -Wmaybe-uninitialized false-positive with -O2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61409 --- Comment #31 from Jeffrey A. Law --- No, it's marked as a regression against gcc-6. One of two things needs to happen for this to be closed. 1. Aldy's work would have to be backported to gcc-6. or 2. gcc-6 goes out of support I don't

[Bug c/87387] trunk/gcc/builtins.c:585:7: warning: -Wself-assign problem

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87387 Jeffrey A. Law changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug middle-end/86540] [9 Regression] pr77445-2.c and ssa-dom-thread-7.c regressions since May 20, 2018

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86540 Jeffrey A. Law changed: What|Removed |Added CC||law at redhat dot com --- Comment #3

[Bug middle-end/87053] wrong code with c_strlen

||law at redhat dot com Resolution|--- |FIXED --- Comment #2 from Jeffrey A. Law --- Fixed by Bernd's patch on the trunk.

[Bug middle-end/86714] tree-ssa-forwprop.c confused by too long initializer

||law at redhat dot com Resolution|--- |FIXED --- Comment #9 from Jeffrey A. Law --- Should be fixed on trunk now.

[Bug middle-end/86711] [9 Regression] wrong folding of memchr

||law at redhat dot com Resolution|--- |FIXED --- Comment #6 from Jeffrey A. Law --- Should be fixed on trunk now.

[Bug middle-end/87009] Can't find XOR pattern applying De Morgan sequentially

||law at redhat dot com Resolution|--- |FIXED --- Comment #4 from Jeffrey A. Law --- Fixed on the trunk.

[Bug tree-optimization/86010] [7/8/9 Regression] redundant memset with smaller size not eliminated

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86010 --- Comment #9 from Jeffrey A. Law --- We don't merge the two memset calls in the second example. It's of arguable value IMHO.

[Bug tree-optimization/87110] [9 Regresssion] tree check fail in to_wide, at tree.h:5523

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87110 Jeffrey A. Law changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug tree-optimization/87110] [9 Regresssion] tree check fail in to_wide, at tree.h:5523

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87110 --- Comment #3 from Jeffrey A. Law --- It's different, but related.

[Bug tree-optimization/87110] [9 Regresssion] tree check fail in to_wide, at tree.h:5523

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87110 Jeffrey A. Law changed: What|Removed |Added CC||law at redhat dot com --- Comment #2

[Bug tree-optimization/87059] [9 Regression] internal compiler error: in set_value_range, at tree-vrp.c:289

||law at redhat dot com Resolution|--- |FIXED --- Comment #23 from Jeffrey A. Law --- Fixed by Martin's patch on the trunk.

[Bug tree-optimization/81958] spurious -Wmaybe-uninitialized warning in gcc-8, or with -O1

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81958 --- Comment #3 from Jeffrey A. Law --- I'd suggest leaving as a single bug for the Wuninitialized issue. There may be other approaches to fixing it that are worth exploring. If we split into multiple bugs for the various hunks of work DOM

[Bug middle-end/86996] [9 regression] gcc.dg/tree-ssa/builtin-sprintf-warn-1.c FAILs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86996 Jeffrey A. Law changed: What|Removed |Added CC||law at redhat dot com --- Comment #3

[Bug target/86547] s390x: Maximum number of LRA assignment passes is achieved (30) when compiling a small inline assembler snippet

||law at redhat dot com Resolution|--- |FIXED --- Comment #9 from Jeffrey A. Law --- Fixed on the trunk.

[Bug middle-end/86897] [9 regression] gcc.dg/uninit-suppress_2.c FAILs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86897 Jeffrey A. Law changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug middle-end/86897] [9 regression] gcc.dg/uninit-suppress_2.c FAILs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86897 --- Comment #2 from Jeffrey A. Law --- Yea, the fix for this was in my tree when I was testing. The DOM changes compromise the test. I'll push my fix to the trunk in a couple hours when I'm back online.

[Bug target/86795] mn10300 port needs updating for CVE-2017-5753

||law at redhat dot com Resolution|--- |FIXED --- Comment #2 from Jeffrey A. Law --- Fixed on the trunk.

[Bug target/86772] [meta-bug] tracking port status for CVE-2017-5753

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772 Bug 86772 depends on bug 86795, which changed state. Bug 86795 Summary: mn10300 port needs updating for CVE-2017-5753 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86795 What|Removed |Added

[Bug tree-optimization/86732] Potential nullptr dereference does not propagate knowledge about the pointer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86732 --- Comment #8 from Jeffrey A. Law --- I wouldn't object to that. In fact I thought we kicked that around along with an option to remove path leading to the undefined behavior completely. But it's not something I'm likely to work on.

[Bug tree-optimization/86732] Potential nullptr dereference does not propagate knowledge about the pointer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86732 Jeffrey A. Law changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug tree-optimization/86732] Potential nullptr dereference does not propagate knowledge about the pointer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86732 Jeffrey A. Law changed: What|Removed |Added CC||law at redhat dot com --- Comment #5

[Bug target/86790] m68k port needs updating for CVE-2017-5753

||law at redhat dot com Resolution|--- |FIXED --- Comment #2 from Jeffrey A. Law --- Fixed on the trunk.

[Bug target/86772] [meta-bug] tracking port status for CVE-2017-5753

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772 Bug 86772 depends on bug 86790, which changed state. Bug 86790 Summary: m68k port needs updating for CVE-2017-5753 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86790 What|Removed |Added

[Bug target/86784] H8 port needs updating for CVE-2017-5753

||law at redhat dot com Resolution|--- |FIXED --- Comment #2 from Jeffrey A. Law --- Fixed on the trunk.

[Bug target/86772] [meta-bug] tracking port status for CVE-2017-5753

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772 Bug 86772 depends on bug 86784, which changed state. Bug 86784 Summary: H8 port needs updating for CVE-2017-5753 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86784 What|Removed |Added

[Bug tree-optimization/69224] [6/7 Regression] -Warray-bounds false positive with -O3 and struct pointer parameter

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69224 --- Comment #13 from Jeffrey A. Law --- Agreed. I don't see a lot of value in backporting this fix to the release branches. One could argue that decision means this should move to CLOSED as it's been fixed for gcc-8 and the trunk.

[Bug target/85993] config/sh/sh.c:10878: suspicious if .. else chain

||law at redhat dot com Resolution|--- |FIXED --- Comment #5 from Jeffrey A. Law --- Fixed on the trunk.

[Bug tree-optimization/86010] [7/8/9 Regression] redundant memset with smaller size not eliminated

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86010 --- Comment #4 from Jeffrey A. Law --- Actually, alignment considerations are really just for head trimming. When trimming the tail we can be more aggressive as residuals are usually handled reasonably efficiently.

[Bug tree-optimization/86010] [7/8/9 Regression] redundant memset with smaller size not eliminated

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86010 --- Comment #3 from Jeffrey A. Law --- It's not an off by 1 error, but a conscious decision to not pass odd addresses into the mem* routines, which are typically doing to emit crappy code for badly aligned data. We correctly see that 7 bytes of

[Bug target/86394] Broken -falign-functions=512 on m68k

||law at redhat dot com Resolution|--- |INVALID --- Comment #1 from Jeffrey A. Law --- No, .align 128 is right AFAICT. .align on the m68k is a byte alignment and requires its argument to be a power of 2.

[Bug tree-optimization/55860] Turn segmented iteration into nested loops

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55860 --- Comment #6 from Jeffrey A. Law --- Doesn't matter much to me either way. I review all the jump threading PRs every release.

[Bug tree-optimization/86339] New: DOM does not handle RHS COND_EXPRs well

-optimization Assignee: unassigned at gcc dot gnu.org Reporter: law at redhat dot com Target Milestone: --- As outlined in this discussion of one of Kugan's patches, DOM does not handle statements like x = COND ? val1 : val2; When COND has a known result. The discussion

[Bug c++/79986] [6/7/8/9 Regression][CHKP] ICE in fold_convert_loc with a flexible array

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79986 --- Comment #11 from Jeffrey A. Law --- I believe it's done. So all the CHKP/MPX bugs can be CLOSED/WONTFIX.

[Bug middle-end/66240] RFE: extend -falign-xyz syntax

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66240 Jeffrey A. Law changed: What|Removed |Added CC||law at redhat dot com --- Comment #8

[Bug debug/84342] Location views breaks cross builds of arm including gnueabihf

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84342 --- Comment #12 from Jeffrey A. Law --- I'm not familiar enough with the ccfsm bits to know if there's something we ought to be doing generically to improve CC handling further. I think downgrading to P2 certainly makes sense though. However,

[Bug tree-optimization/85964] [8/9 Regression] compile time hog w/ -O3 -ftracer -fno-guess-branch-probability

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85964 Jeffrey A. Law changed: What|Removed |Added CC||law at redhat dot com --- Comment #13

[Bug tree-optimization/85478] ICE with single element vector

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85478 Jeffrey A. Law changed: What|Removed |Added CC||law at redhat dot com --- Comment #11

[Bug target/84923] [8 regression] gcc.dg/attr-weakref-1.c failed on aarch64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84923 Jeffrey A. Law changed: What|Removed |Added CC||law at redhat dot com

[Bug tree-optimization/82665] missing value range optimization for memchr

||law at redhat dot com Resolution|--- |FIXED --- Comment #4 from Jeffrey A. Law --- Fixed on the trunk.

[Bug tree-optimization/77485] Missed dead store elimination of aggregate store followed by partial stores

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77485 Bug 77485 depends on bug 33562, which changed state. Bug 33562 Summary: [6 Regression] aggregate DSE disabled https://gcc.gnu.org/bugzilla/show_bug.cgi?id=33562 What|Removed |Added

[Bug tree-optimization/33562] [6 Regression] aggregate DSE disabled

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=33562 Jeffrey A. Law changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug tree-optimization/85259] [8 Regression] Missing -Wstringop-overflow= since r256683

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85259 Jeffrey A. Law changed: What|Removed |Added CC||law at redhat dot com Target

[Bug tree-optimization/85301] bitfield check causes maybe-uninitialized warning

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85301 Jeffrey A. Law changed: What|Removed |Added CC||law at redhat dot com --- Comment #7

[Bug tree-optimization/85301] bitfield check causes maybe-uninitialized warning

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85301 --- Comment #5 from Jeffrey A. Law --- FWIW, there's another similar bug where DOM doesn't do a particularly good job at tracking the state of objects implied the results of logical operations which in turn causes missed optimizations. I've

[Bug tree-optimization/85186] jump threading can rotate loops affecting loop form, and causing vectorization not to happen

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85186 Jeffrey A. Law changed: What|Removed |Added CC||law at redhat dot com --- Comment #6

[Bug tree-optimization/79958] Missed tree DSE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79958 Jeffrey A. Law changed: What|Removed |Added CC||law at redhat dot com --- Comment #3

[Bug c/84919] [8 Regression] error: passing argument 1 to restrict-qualified parameter aliases with argument 5 [-Werror=restrict]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84919 Jeffrey A. Law changed: What|Removed |Added Target Milestone|8.0 |9.0 --- Comment #13 from Jeffrey A.

[Bug tree-optimization/84933] [8 Regression] ICE in set_value_range, at tree-vrp.c:288 since r257852

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

[Bug c/84919] [8 Regression] error: passing argument 1 to restrict-qualified parameter aliases with argument 5 [-Werror=restrict]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84919 Jeffrey A. Law changed: What|Removed |Added CC||law at redhat dot com --- Comment #3

[Bug target/84876] [8 Regression] ICE on invalid code in lra_assign at gcc/lra-assigns.c:1601 since r258504

||law at redhat dot com Resolution|--- |FIXED --- Comment #5 from Jeffrey A. Law --- Fixed by Vlad's commit on the trunk.

[Bug target/70359] [6/7/8 Regression] Code size increase for x86/ARM/others compared to gcc-5.3.0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70359 --- Comment #36 from Jeffrey A. Law --- WRT the division removal. That seems so profitable that a slight increase in codesize is warranted. So if we fix the other issue and the source of the remaining codesize regressions is the removal of

[Bug tree-optimization/84526] [8 Regression] ICE in generic_overlap at gcc/gimple-ssa-warn-restrict.c:927 since r257860

||law at redhat dot com Resolution|--- |FIXED --- Comment #12 from Jeffrey A. Law --- Fixed by Martin's patch on the trunk.

[Bug rtl-optimization/84682] [6/7 Regression] internal compiler error: Segmentation fault (process_address_1)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84682 Jeffrey A. Law changed: What|Removed |Added CC||law at redhat dot com

[Bug tree-optimization/84670] [8 Regression] ICE: in compute_antic_aux, at tree-ssa-pre.c:2148 with -O2 -fno-tree-dominator-opts

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84670 Jeffrey A. Law changed: What|Removed |Added CC||law at redhat dot com --- Comment #5

[Bug tree-optimization/84515] missed optimization: expected loop merging

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84515 Jeffrey A. Law changed: What|Removed |Added CC||law at redhat dot com --- Comment #4

[Bug tree-optimization/84646] Missed optimisation for hoisting conditions outside nested loops

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84646 Jeffrey A. Law changed: What|Removed |Added CC||law at redhat dot com --- Comment #2

[Bug target/70359] [6/7/8 Regression] Code size increase for ARM compared to gcc-5.3.0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70359 --- Comment #27 from Jeffrey A. Law --- Yea, we went through similar issues with Alex's work recently. After that work landed I went through all the BZs that I could find with autoinc {pre,post}{inc,dec} that BZ could find in the hopes that his

[Bug tree-optimization/57534] [6/7/8 Regression]: Performance regression versus 4.7.3, 4.8.1 is ~15% slower

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57534 Jeffrey A. Law changed: What|Removed |Added Target Milestone|6.5 |9.0 --- Comment #30 from Jeffrey A.

[Bug tree-optimization/57534] [6/7/8 Regression]: Performance regression versus 4.7.3, 4.8.1 is ~15% slower

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57534 --- Comment #28 from Jeffrey A. Law --- BTW, ISTM that we need Bin to chime in on the complexity of improving this in IVOPTS -- ie, is it gcc-8 or gcc-9 material. If the latter, then we should adjust the target milestone.

[Bug tree-optimization/57534] [6/7/8 Regression]: Performance regression versus 4.7.3, 4.8.1 is ~15% slower

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57534 --- Comment #27 from Jeffrey A. Law --- WRT c#21. There is a good paper from Click on an integrated GVN/GCM/reassoc. "Combining Analyses, Combining Optimizations" It was published in PLDI. I've probably got a copy here if you want it.

[Bug target/66433] Arm NEON postincrement optimization missed

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66433 Jeffrey A. Law changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug target/66433] Arm NEON postincrement optimization missed

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66433 Jeffrey A. Law changed: What|Removed |Added CC||law at redhat dot com --- Comment #3

[Bug target/82248] probe_stack can generate unpredictable STR on arm

||law at redhat dot com Resolution|--- |FIXED --- Comment #7 from Jeffrey A. Law --- Fixed by Ramana's patch on the trunk.

[Bug tree-optimization/57534] [6/7/8 Regression]: Performance regression versus 4.7.3, 4.8.1 is ~15% slower

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57534 --- Comment #18 from Jeffrey A. Law --- A couple more notes. It could also well be the case that reassociating in a way that encourages lea could be good for x86, but bad for other targets. I also suspect this is closely related to other BZs

[Bug tree-optimization/57534] [6/7/8 Regression]: Performance regression versus 4.7.3, 4.8.1 is ~15% slower

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57534 --- Comment #17 from Jeffrey A. Law --- It could well end up being a case where we need to look to see if the expressions are likely to CSE to determine which is better. I'm not sure if reassoc has that kind of capability.

[Bug target/83496] [7/8 regression] wrong code generated with -Os -mbranch-cost=1

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83496 --- Comment #33 from Jeffrey A. Law --- No. THe one I'm currently chasing is not 84545. I'm chasing a ton of ICEs due to debug insns appearing in places we didn't expect.

[Bug target/83496] [7/8 regression] wrong code generated with -Os -mbranch-cost=1

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83496 --- Comment #30 from Jeffrey A. Law --- Just a note. I'm tracking a separate problem with delay slot filling that looks like it's related to handling of debug insns. I doubt it's the same problem, but if you stumble over it, be aware I'm

[Bug fortran/84523] [8 Regression] Runtime crash deallocating allocatable array within derived type

||law at redhat dot com

[Bug middle-end/61118] [6/7/8 Regression] Indirect call generated for pthread_cleanup_push with constant cleanup function

at gcc dot gnu.org |law at redhat dot com

[Bug middle-end/21161] [6/7/8 Regression] "clobbered by longjmp" warning ignores the data flow

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=21161 Jeffrey A. Law changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |law at redhat dot com

[Bug middle-end/61118] [6/7/8 Regression] Indirect call generated for pthread_cleanup_push with constant cleanup function

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61118 --- Comment #23 from Jeffrey A. Law --- Note that if we fix the abnormal handler to target the block after the setjmp rather than the setjmp itself all the problems magically disappear. That's actually a more accurate CFG and arguably the right

[Bug middle-end/65041] Improve -Wclobbered

||law at redhat dot com Resolution|DUPLICATE |--- --- Comment #6 from Jeffrey A. Law --- The warning on a2 is clearly bogus. ISTM we ought to get a warning on fd, but don't because it's associated DECL_RTL is not set. It almost feels like instead

[Bug middle-end/61118] [6/7/8 Regression] Indirect call generated for pthread_cleanup_push with constant cleanup function

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61118 Jeffrey A. Law changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|DUPLICATE

<    1   2   3   4   5   6   7   8   9   10   >