https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89856
--- Comment #3 from Daniel Vollmer ---
These linker warnings then also seem to result in actual address-sanitizer
errors (which may or may not be spurious):
(Output not from the provided example, but the shown
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89856
--- Comment #2 from Daniel Vollmer ---
I'm seeing the same warning in a similar context when using the
address-sanitizer, e.g.
> cat lib.cpp
#include
#include
inline const std::string ()
{
static const std::string str = "abc";
return
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68771
--- Comment #26 from Daniel Vollmer ---
(In reply to Iain Sandoe from comment #25)
> (In reply to Daniel Vollmer from comment #24)
> > (In reply to Iain Sandoe from comment #23)
> >
> > > My freshly-built 7.4 (bootstrapped with 10.1 xc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68771
--- Comment #24 from Daniel Vollmer ---
(In reply to Iain Sandoe from comment #23)
> My freshly-built 7.4 (bootstrapped with 10.1 xc effectively) doesn't
> reproduce it, neither do any other branches I have lying around - so we're
> not there
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68771
--- Comment #22 from Daniel Vollmer ---
(In reply to Iain Sandoe from comment #21)
> > I rebuilt 7.4.0 locally just now (so in 10.14.4), and now I can no longer
> > reproduce the problem. I'm not sure what could cause the difference,
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68771
--- Comment #20 from Daniel Vollmer ---
Interesting. The gcc-7.4.0 was the bottled (precompiled) version from homebrew,
generated on Dec 7th 2018, so I assume it must've been built on 10.14.1 or
10.14.2.
I rebuilt 7.4.0 locally just now (so in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68771
--- Comment #18 from Daniel Vollmer ---
(In reply to Iain Sandoe from comment #17)
> hmm. this one is not repeating for me - please can you tell me:
> OS version and the svn rev (or GIT sha1) for the version of 7 branch that
> you're using?
> (I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68771
--- Comment #16 from Daniel Vollmer ---
Created attachment 46038
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46038=edit
reproducer for threading issue -fprofile-generate
The attached example (see comments for command-lines) yields the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68771
--- Comment #14 from Daniel Vollmer ---
(In reply to Iain Sandoe from comment #13)
> Please pick one - and make a new PR for the second (probably this stuff
> is quite self-contained and could be split out) ... we can then retitle the
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89856
--- Comment #1 from Daniel Vollmer ---
Initial analysis from Iain Sandoe
> OK (initial analysis). what we have is
>
> __ZGVZ19BroadcastFromMasterImEvPT_mE4bufs:
> .space 8
>
>
> LPX0:
>
>
> and then a reference to LPX0 in
Product: gcc
Version: 7.4.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: zerolo at gmail dot com
Target Milestone: ---
Created attachment 46037
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68771
--- Comment #11 from Daniel Vollmer ---
(In reply to Iain Sandoe from comment #9)
> (In reply to Daniel Vollmer from comment #8)
> > Using g++-7.4.0 I'm now seeing the following:
> > - Step 1) (the compilation with "-flto -fprofile-generate")
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68771
--- Comment #10 from Daniel Vollmer ---
Created attachment 46036
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46036=edit
Example triggering "This was likely caused by different translation units being
compiled with different visibility
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68771
--- Comment #8 from Daniel Vollmer ---
Using g++-7.4.0 I'm now seeing the following:
- Step 1) (the compilation with "-flto -fprofile-generate") still works,
including the visibility warnings mentioned in Comment #2, in particular
ld: warning:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68771
--- Comment #6 from Daniel Vollmer ---
Is 7.4 or 8.3 new enough to be worthwhile trying?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68771
--- Comment #2 from Daniel Vollmer ---
I'm having even more trouble to get this to work using a current gcc-7
(Homebrew GCC 7.3.0) 7.3.0.
First, I see some warnings in step 1) of the form
ld: warning: direct access in function
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60796
--- Comment #4 from Daniel Vollmer ---
The relevant clang issue seems to be
https://llvm.org/bugs/show_bug.cgi?id=22763
In my case, I have the "extern template" declaration in the header for the
corresponding template, thus preventing any
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60796
Daniel Vollmer changed:
What|Removed |Added
CC||zerolo at gmail dot com
--- Comment #2
Severity: normal
Priority: P3
Component: debug
Assignee: unassigned at gcc dot gnu.org
Reporter: zerolo at gmail dot com
Target Milestone: ---
Created attachment 36944
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36944=edit
Patch to make cold sect
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65995
--- Comment #7 from Daniel Vollmer ---
Crash still present in gcc 5.3.0.
When compiling with -g I also get plenty of the warnings for pretty much each
and every symbol used in the library / program, e.g.
[snip hundreds more]
warning: (x86_64)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65995
Daniel Vollmer zerolo at gmail dot com changed:
What|Removed |Added
CC||zerolo at gmail
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: zerolo at gmail dot com
Target Milestone: ---
Created attachment 35731
-- https://gcc.gnu.org/bugzilla/attachment.cgi?id=35731action=edit
repo that compiles with g++-4.9.2 -std=c++11
22 matches
Mail list logo
