https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114699
--- Comment #3 from Richard W.M. Jones ---
(Edit comment 2: To be clear, that wasn't the thread where the
segfault occurred, which was some golang thread, that was the
thread that was unmapping the memory at the same time. Using
nodelete avoids
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114699
--- Comment #2 from Richard W.M. Jones ---
This was the stack trace of the crashing thread with gcc-go:
Thread 7 (Thread 0x7ff5c1af3a40 (LWP 2819340)):
#0 0x7ff5c24d67cb in __GI_munmap () at
../sysdeps/unix/syscall-template.S:117
#1 0x000
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114699
--- Comment #1 from Richard W.M. Jones ---
gcc 14.0.1-0.13.fc40 => crashes
golang-bin-1.22.2-1.fc40.x86_64 => works
I also checked this by stracing the linking process and
seeing -Wl,-z,nodelete is being used by golang, but not by
gcc-go.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114699
Bug ID: 114699
Summary: gcc-go -buildmode=c-shared doesn't use -Wl,-z,nodelete
so libraries crash when dlclosed
Product: gcc
Version: 14.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104158
Richard W.M. Jones changed:
What|Removed |Added
CC||rjones at redhat dot com
--- Comme
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103395
--- Comment #1 from Richard W.M. Jones ---
Nice reproducer!
Here's the original thread where the bug was reported when compiling qemu on
Fedora Rawhide for armv7:
https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/threa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102233
--- Comment #5 from Richard W.M. Jones ---
(In reply to David Malcolm from comment #4)
> (In reply to Richard W.M. Jones from comment #2)
> > I think since this seems to be LTO-related, you probably do need
> > to use LTO CFLAGS in the initial .
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102233
--- Comment #2 from Richard W.M. Jones ---
I think since this seems to be LTO-related, you probably do need
to use LTO CFLAGS in the initial ./configure step. My actual CFLAGS
were:
export CFLAGS="$(rpm --eval '%{optflags}')"
export CXXFLAGS="
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102233
--- Comment #1 from Richard W.M. Jones ---
perf top shows:
36.63% lto1 [.] shortest_paths::shortest_paths
which it pretty much stuck permanently at 30-50% CPU. The
machine has plenty of free memory and is not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102233
Bug ID: 102233
Summary: Compiling a smallish binary with -fanalyzer seems to
cause very very long compile times
Product: gcc
Version: unknown
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99260
--- Comment #6 from Richard W.M. Jones ---
That's excellent news, thanks. We'll get around to trying this
when GCC 12 appears in Rawhide.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99716
--- Comment #3 from Richard W.M. Jones ---
FYI the original code is:
https://github.com/libguestfs/libguestfs/blob/e0a11061035d47b118c95706240bcc17fd576edc/tests/mount-local/test-parallel-mount-local.c#L299-L335
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99716
Bug ID: 99716
Summary: -Wanalyzer-double-fclose when fclose is called inside
a loop
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Pr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99193
--- Comment #12 from Richard W.M. Jones ---
There are quite a lot of these - I will try removing them
when we get the updated GCC in Fedora.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99193
--- Comment #10 from Richard W.M. Jones ---
Great stuff, I'll give this a go when GCC is updated
in Fedora Rawhide.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99196
--- Comment #3 from Richard W.M. Jones ---
Note if errcode == 0 then error does NOT exit :-)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99193
--- Comment #4 from Richard W.M. Jones ---
And another:
https://github.com/libguestfs/libguestfs/blob/f19fd566f6387ce7e4d82409528c9dde374d25e0/daemon/debug.c#L115
debug.c: In function 'debug_help':
debug.c:129:9: error: 'r' should have been deal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99196
Bug ID: 99196
Summary: GCC analyzer doesn't know that error (code != 0, ...)
exits the program
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: norma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99193
--- Comment #3 from Richard W.M. Jones ---
This seems to be the same thing at a different place in the code:
https://github.com/libguestfs/libguestfs/blob/f19fd566f6387ce7e4d82409528c9dde374d25e0/df/main.c#L404
CC virt_df-main.o
main.c:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99193
Richard W.M. Jones changed:
What|Removed |Added
Version|unknown |11.0
--- Comment #2 from Richard W.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99193
--- Comment #1 from Richard W.M. Jones ---
Created attachment 50232
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50232&action=edit
preprocessed source (xz compressed)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99193
Bug ID: 99193
Summary: Bogus "should have been deallocated with 'free' but
was deallocated with 'realloc' [CWE-762]
[-Werror=analyzer-mismatching-deallocation]"
Product: gcc
22 matches
Mail list logo
