https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80551
Martin Liška changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80551
--- Comment #20 from Martin Liška ---
Author: marxin
Date: Tue Mar 6 20:07:49 2018
New Revision: 258300
URL: https://gcc.gnu.org/viewcvs?rev=258300&root=gcc&view=rev
Log:
Backport r257932
2018-03-06 Martin Liska
Backport from mainl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80551
Segher Boessenkool changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80551
Segher Boessenkool changed:
What|Removed |Added
Version|7.0 |8.0
Depends on|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80551
Martin Liška changed:
What|Removed |Added
Status|NEW |RESOLVED
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80551
--- Comment #16 from Segher Boessenkool ---
Fixed on trunk. Does this actually fail on GCC 7? The regexp there should
work AFAICS.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80551
--- Comment #15 from Segher Boessenkool ---
Author: segher
Date: Fri Feb 23 14:17:35 2018
New Revision: 257932
URL: https://gcc.gnu.org/viewcvs?rev=257932&root=gcc&view=rev
Log:
Fix tsan race_on_mutex.c testcase (PR80551)
The testcase did not m
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80551
--- Comment #14 from Jakub Jelinek ---
Changing that (__)? to ((__GI_)?__)? is preapproved if it works.
Those are just glibc internal aliases which are in the symbol table too though,
so if you have full debug info for libpthread.so rather than j
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80551
--- Comment #13 from Segher Boessenkool ---
It is trying to match
#[01] (__)?pthread_mutex_init
but instead it gets
#1 __GI___pthread_mutex_init
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80551
--- Comment #12 from Segher Boessenkool ---
It does break if I set the breakpoints before the shared libs have loaded.
Thread 3 "a.out" hit Breakpoint 1, 0x3fffb6e0c860 in .__memset_power7 ()
from /lib64/libc.so.6
#0 0x3fffb6e0c860
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80551
Segher Boessenkool changed:
What|Removed |Added
Status|WAITING |NEW
--- Comment #11 from Segher Boe
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80551
--- Comment #10 from Martin Liška ---
(In reply to Segher Boessenkool from comment #9)
> Nothing, it never reaches memset before it exits.
Are you sure? I was able to place breakpoint on memset and ~14th iteration of
the breakpoint was really mu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80551
--- Comment #9 from Segher Boessenkool ---
Nothing, it never reaches memset before it exits.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80551
Martin Liška changed:
What|Removed |Added
Target Milestone|--- |8.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80551
Martin Liška changed:
What|Removed |Added
Status|NEW |WAITING
--- Comment #8 from Martin Liška
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80551
--- Comment #7 from Segher Boessenkool ---
Why can't the unwinder find the function name here?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80551
--- Comment #6 from Martin Liška ---
(In reply to Segher Boessenkool from comment #5)
> Why disable it? Can the feature not work, can the test not work?
>
> Disabling the test is papering over the problem as far as I see.
The test does not wor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80551
--- Comment #5 from Segher Boessenkool ---
Why disable it? Can the feature not work, can the test not work?
Disabling the test is papering over the problem as far as I see.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80551
--- Comment #4 from Martin Liška ---
(In reply to Segher Boessenkool from comment #3)
> It apparently started failing last week of January 2017. Only 64-bit
> fails, -m32 is fine.
>
> I don't know where that missing function name is coming from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80551
--- Comment #3 from Segher Boessenkool ---
It apparently started failing last week of January 2017. Only 64-bit
fails, -m32 is fine.
I don't know where that missing function name is coming from.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80551
--- Comment #2 from Martin Liška ---
Segher any investigation about this?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80551
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
22 matches
Mail list logo