https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116885
Jeffrey Walton changed:
What|Removed |Added
CC||noloader at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84508
--- Comment #23 from Jeffrey Walton ---
(In reply to Peter Cordes from comment #22)
> [...]
> That instruction is useless and should never be used in asm except for
> code-alignment reasons (1 byte longer than MOVLPS, same length as MOVSD, all
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81358
--- Comment #13 from Jeffrey Walton ---
Add a mee too. When using sanitizers, like -fsanitize=undefined, the compiler
driver is not adding the necessary libraries to link the program. Ugh...
https://github.com/weidai11/cryptopp/issues/1141#issue
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106568
--- Comment #20 from Jeffrey Walton ---
Hi Andrew.
I went through the list of options that are enabled at -O2 from [1]. I built
the library with each option separately at "-DNDEBUG -g2 -O2 -fno-xxx".
Here is the list of suspects. I seem to rec
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106568
--- Comment #19 from Jeffrey Walton ---
Created attachment 53427
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53427&action=edit
Test script to build library at -O2 with -fno-xxx
Test script to build library at -O2 with -fno-xxx
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106568
--- Comment #18 from Jeffrey Walton ---
(In reply to Andrew Pinski from comment #17)
> The other thing to try is -fstack-reuse=none.
No joy with -fstack-reuse=none. The crash is still present.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106568
--- Comment #15 from Jeffrey Walton ---
It looks like -fno-strict-aliasing cleared the crash. This is bad because I
thought we did not violate aliasing rules.
Let me try to find it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106568
--- Comment #14 from Jeffrey Walton ---
(In reply to Jeffrey Walton from comment #13)
> (In reply to Andrew Pinski from comment #12)
> > Can you try -fno-reorder-blocks-and-partition adding to the options?
> > This would not be the first time th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106568
--- Comment #13 from Jeffrey Walton ---
(In reply to Andrew Pinski from comment #12)
> Can you try -fno-reorder-blocks-and-partition adding to the options?
> This would not be the first time this option caused issues with EH.
No joy with -fno-r
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106568
--- Comment #10 from Jeffrey Walton ---
I'm not sure if this is helpful, but Valgrind is showing invalid reads in the
unwind gear:
$ valgrind ./cryptest.exe vv 51
==27339== Memcheck, a memory error detector
==27339== Copyright (C) 2002-2022, an
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106568
--- Comment #9 from Jeffrey Walton ---
(In reply to Andrew Pinski from comment #8)
> (In reply to Jeffrey Walton from comment #7)
>
> Try putting a breakpoint on the following functions:
> _Unwind_RaiseException
> _Unwind_ForcedUnwind
> _Unwind
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106568
--- Comment #7 from Jeffrey Walton ---
(In reply to Andrew Pinski from comment #6)
> >And the program does not take the exception path. Instead it segfaults.
>
> If I read the backtrace correctly, it is trying to resume an unwind because
> it d
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106568
--- Comment #5 from Jeffrey Walton ---
(In reply to Andrew Pinski from comment #3)
> Though there might be an EH issue but there has not been an EH issue for a
> long time .
This is an interesting observation.
The stack trace shows frame #0 is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106568
Bug ID: 106568
Summary: -freorder-blocks-algorithm appears to causes a crash
in stable code, no way to disable it
Product: gcc
Version: 12.1.1
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104455
Jeffrey Walton changed:
What|Removed |Added
Resolution|INVALID |FIXED
--- Comment #4 from Jeffrey Walt
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104455
--- Comment #2 from Jeffrey Walton ---
(In reply to Richard Earnshaw from comment #1)
> What's the configuration of the compiler? Eg, the output of gcc -v
Thanks Richard. I set-up a Debian Qemu/Chroot for armhf. I can now duplicate
the problem
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104455
Bug ID: 104455
Summary: Cannot select -march=armv7-a using GCC 11
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103863
--- Comment #2 from Jeffrey Walton ---
(In reply to Andrew Pinski from comment #1)
> I think the warning needs to be implemented in the linker rather than in GCC
> because the linker is what decides if there are executable stacks are needed
> or
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103863
Bug ID: 103863
Summary: We need a warning for loss of no-exec stacks
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96168
Jeffrey Walton changed:
What|Removed |Added
CC||noloader at gmail dot com
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82735
--- Comment #6 from Jeffrey Walton ---
Add 9.3 to the know to fail list:
$ gcc --version
gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Copyright (C) 2019 Free Software Foundation, Inc.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82735
--- Comment #5 from Jeffrey Walton ---
I think we are seeing this bug in the field. We are catching lots of failed
self tests as we test on multiple platforms, including Ubuntu 14 ERS and Ubuntu
16 LTS.
The problem makes GCC 4.8.4 through 7.5 pr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53431
--- Comment #40 from Jeffrey Walton ---
Still a problem in 2021.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98416
--- Comment #3 from Jeffrey Walton ---
(In reply to Andrew Pinski from comment #2)
> This is invalid.
> The instruction which is failing is:
> 9c: f0 00 02 d0 xxspltib vs0,0
>
> Which is only valid in power9 and above.
> You need to mark CP
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98416
--- Comment #1 from Jeffrey Walton ---
Created attachment 49831
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49831&action=edit
Disassembly of ppc_power9.o
Created with 'objdump --disassemble ppc_power9.o | c++filt >
ppc_power9.disass'.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98416
Bug ID: 98416
Summary: POWER8: SIGILL handler does not restart properly after
signal using GCC 10.2.1
Product: gcc
Version: 10.2.1
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93644
--- Comment #13 from Jeffrey Walton ---
On Wed, Dec 16, 2020 at 9:05 PM eggert at cs dot ucla.edu
wrote:
> ...
> (B) there's no way to shut off the false alarm, not even with '# pragma GCC
> diagnostic ignored "-Wreturn-local-addr"'.
https://gc
27 matches
Mail list logo
