public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
* [Bug debug/112674] New: [14 Regression] Compare-debug failure after recent change on c6x @ 2023-11-22 23:02 law at gcc dot gnu.org 2023-11-22 23:05 ` [Bug debug/112674] " law at gcc dot gnu.org ` (2 more replies) 0 siblings, 3 replies; 4+ messages in thread From: law at gcc dot gnu.org @ 2023-11-22 23:02 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112674 Bug ID: 112674 Summary: [14 Regression] Compare-debug failure after recent change on c6x Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: debug Assignee: unassigned at gcc dot gnu.org Reporter: law at gcc dot gnu.org Target Milestone: --- This patch: commit 6bf66276e3e41d5d92f7b7260e98b6a111653805 Author: Richard Biener <rguenther@suse.de> Date: Wed Nov 22 11:10:41 2023 +0100 tree-optimization/112344 - wrong final value replacement When performing final value replacement chrec_apply that's used to compute the overall effect of niters to a CHREC doesn't consider that the overall increment of { -2147483648, +, 2 } doesn't fit in a signed integer when the loop iterates until the value of the IV of 20. The following fixes this mistake, carrying out the multiply and add in an unsigned type instead, avoiding undefined overflow and thus later miscompilation by path range analysis. PR tree-optimization/112344 * tree-chrec.cc (chrec_apply): Perform the overall increment calculation and increment in an unsigned type. * gcc.dg/torture/pr112344.c: New testcase. Is causing a compare-debug failure on the c6x port: c6x-sim: gcc.dg/pr65779.c (test for excess errors) I haven't dug into this any deeper. It could well be a c6x bug in the end. While it may sound similar to pr109777, pr109777 has been debugged far enough to lay the blame on the bfin backend. ^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug debug/112674] [14 Regression] Compare-debug failure after recent change on c6x 2023-11-22 23:02 [Bug debug/112674] New: [14 Regression] Compare-debug failure after recent change on c6x law at gcc dot gnu.org @ 2023-11-22 23:05 ` law at gcc dot gnu.org 2023-11-23 8:29 ` rguenth at gcc dot gnu.org 2023-11-24 7:51 ` rguenth at gcc dot gnu.org 2 siblings, 0 replies; 4+ messages in thread From: law at gcc dot gnu.org @ 2023-11-22 23:05 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112674 --- Comment #1 from Jeffrey A. Law <law at gcc dot gnu.org> --- And possibly more interesting than the compare-debug failure is this patch seems to be causing Wstringop-overflow-17 to fail on multiple targets, including c6x. ^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug debug/112674] [14 Regression] Compare-debug failure after recent change on c6x 2023-11-22 23:02 [Bug debug/112674] New: [14 Regression] Compare-debug failure after recent change on c6x law at gcc dot gnu.org 2023-11-22 23:05 ` [Bug debug/112674] " law at gcc dot gnu.org @ 2023-11-23 8:29 ` rguenth at gcc dot gnu.org 2023-11-24 7:51 ` rguenth at gcc dot gnu.org 2 siblings, 0 replies; 4+ messages in thread From: rguenth at gcc dot gnu.org @ 2023-11-23 8:29 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112674 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2023-11-23 Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 Target Milestone|--- |14.0 --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- I will have a look. ^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug debug/112674] [14 Regression] Compare-debug failure after recent change on c6x 2023-11-22 23:02 [Bug debug/112674] New: [14 Regression] Compare-debug failure after recent change on c6x law at gcc dot gnu.org 2023-11-22 23:05 ` [Bug debug/112674] " law at gcc dot gnu.org 2023-11-23 8:29 ` rguenth at gcc dot gnu.org @ 2023-11-24 7:51 ` rguenth at gcc dot gnu.org 2 siblings, 0 replies; 4+ messages in thread From: rguenth at gcc dot gnu.org @ 2023-11-24 7:51 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112674 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- Fixed. ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2023-11-24 7:51 UTC | newest] Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2023-11-22 23:02 [Bug debug/112674] New: [14 Regression] Compare-debug failure after recent change on c6x law at gcc dot gnu.org 2023-11-22 23:05 ` [Bug debug/112674] " law at gcc dot gnu.org 2023-11-23 8:29 ` rguenth at gcc dot gnu.org 2023-11-24 7:51 ` rguenth at gcc dot gnu.org
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).