https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115010
Jeffrey A. Law changed:
What|Removed |Added
Last reconfirmed|2024-05-09 00:00:00 |2025-03-02
Status|UNCONFIR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115010
--- Comment #19 from Thorsten Otto ---
Bisecting gave me:
>From dba20679f1bf138ab5e61ad131b887db42083174 Mon Sep 17 00:00:00 2001
From: Xianmiao Qu
Date: Sun, 25 Aug 2024 11:22:21 -0600
Subject: [PATCH] [PATCH] Re-add calling emit_clobber in l
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115010
--- Comment #18 from Thorsten Otto ---
Confirmed. I'll try to bisect which commit caused the error to disappear,
starting with commit 77ccfa6ac8d6e4dfefdea45c4259a2873ff9eb3d
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115010
--- Comment #17 from Andreas Schwab ---
I'm not able to reproduce the error with current trunk, with or without LRA.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115010
--- Comment #16 from Thorsten Otto ---
Yes, i'm just curious what that "latent bug" might be.
It might not have to do directly with that __builtin_mul_overflow() at all,
because when using -m68060, library calls to __mulsi3() are used to avoid
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115010
--- Comment #15 from Andrew Pinski ---
(In reply to Thorsten Otto from comment #14)
> A bisect between 10.0.0 and 11.4.0 for the 2nd testcase gave me this commit:
>
> commit 512c6ba04102295fccc62a173ee0086ca733c920
> From: Richard Biener
> Dat
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115010
--- Comment #14 from Thorsten Otto ---
A bisect between 10.0.0 and 11.4.0 for the 2nd testcase gave me this commit:
commit 512c6ba04102295fccc62a173ee0086ca733c920
From: Richard Biener
Date: Thu, 12 Nov 2020 11:29:12 +0100
Subject: [PATCH] Avo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115010
--- Comment #13 from Thorsten Otto ---
Now its getting really strange. I've attached a 2nd test case above. With that,
the bug can be reproduced also with gcc 11.4.0 (but not with gcc-10, gcc-12 or
gcc-13).
It is slightly larger than the first
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115010
--- Comment #12 from Thorsten Otto ---
Created attachment 58187
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58187&action=edit
2nd test case
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115010
--- Comment #11 from Thorsten Otto ---
Confirmed, reverting that commit will prevent the error. Now the question is
how to find the real cause of the problem, since reverting that commit is most
likely not the solution. OTOH, it would be nice to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115010
Mikael Pettersson changed:
What|Removed |Added
CC||mikpelinux at gmail dot com
--- Com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115010
--- Comment #9 from Thorsten Otto ---
Doing some more testing:
- a cross-compiler build for m68k-suse-linux gives the same error on the
reduced testcase
- the error only occurs when using -m68020-60 or -m68060
- older compiler versions (tested
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115010
--- Comment #8 from Thorsten Otto ---
I've never use cvise before, but it gave the attached short source. It inserted
a strange recursive call at the end, but it gives me these error messages:
test.c: In function 'void mul_hwi(bool*)':
test.c:4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115010
--- Comment #7 from Thorsten Otto ---
Created attachment 58151
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58151&action=edit
Shortened test case
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115010
--- Comment #6 from Thorsten Otto ---
Oh, yes, of course.
command line that failed:
m68k-atari-mint-g++-14.1.0 -m68020-60 "-fno-PIE" "-c" "-O2"
"-fomit-frame-pointer" "-DIN_GCC" "-fno-exceptions" "-fno-rtti"
"-fasynchronous-unwind-tables" "-W"
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115010
Sam James changed:
What|Removed |Added
CC||sjames at gcc dot gnu.org
--- Comment #5 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115010
Andrew Pinski changed:
What|Removed |Added
Status|WAITING |UNCONFIRMED
Ever confirmed|1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115010
--- Comment #4 from Thorsten Otto ---
Created attachment 58150
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58150&action=edit
preprocessed source & assembler output of tree-data-ref.cc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115010
Andrew Pinski changed:
What|Removed |Added
Target||m68k-linux-gnu
Status|UNCON
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115010
--- Comment #2 from Thorsten Otto ---
Yes, i'm aware of that. And as already mentioned, the bug is not triggered by
all gcc versions. Is there something i can do to track down the issue?
tree-data-ref.cc is quite large.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115010
--- Comment #1 from Andreas Schwab ---
The m,0,s alternative exists since the beginning.
21 matches
Mail list logo
