https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66312
--- Comment #8 from John Paul Adrian Glaubitz ---
Would it be helpful to have a diff of the disassembly attached to this bug
report as in PR target/67002?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66312
--- Comment #9 from Oleg Endo ---
(In reply to John Paul Adrian Glaubitz from comment #8)
> Would it be helpful to have a diff of the disassembly attached to this bug
> report as in PR target/67002?
Yes, maybe. Please attach.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67092
vries at gcc dot gnu.org changed:
What|Removed |Added
Summary|bootstrap failure with |bootstrap failure in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66511
--- Comment #2 from Matthijs Kooijman ---
So, IIUC, this is quite hard to fix? Either you use lib functions, which
prevents the optimizer from just relabeling or coyping registers to apply
shifting, or you don't and then more complex operations w
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67094
Bug ID: 67094
Summary: Compiling and linking through compiler driver with '-x
c++' fails to link with stream of errors
Product: gcc
Version: 5.1.1
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67095
Bug ID: 67095
Summary: errno for logf(-1.f)
Product: gcc
Version: 4.8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67094
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67094
--- Comment #2 from Andrew Pinski ---
That -x c++ with .o files are being treated as c++ source and being compiled
and that is what is the error message is saying. The .o file is a binary file.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67095
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67094
--- Comment #3 from Jeffrey Walton ---
(In reply to Andrew Pinski from comment #2)
> That -x c++ with .o files are being treated as c++ source and being compiled
> and that is what is the error message is saying. The .o file is a binary
> file.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67096
Bug ID: 67096
Summary: libstdc++ testsuite, codecvt: many UTF-8 tests illegal
(testing bytes 5 and 6)
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Severity: no
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67096
--- Comment #1 from John Marino ---
Created attachment 36108
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36108&action=edit
modification to test that makes it legal
As an illustration, I've modified the test to stop before 0x20 which
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67092
H.J. Lu changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67092
--- Comment #4 from vries at gcc dot gnu.org ---
(In reply to H.J. Lu from comment #3)
> Only build/genpreds in stage1 should be linked with libstdc++.so.6.
Why?
> Why are build/genpreds in stage2 and stage2 linked with libstdc++.so.6?
AFAICT,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67093
--- Comment #2 from Martin Sebor ---
Yes, that's the latest POSIX spec. The term "should" is defined in section 1.5
Terminology as:
...
For an application, describes a feature or behavior that is recommended
programming practice for optimu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67092
--- Comment #5 from H.J. Lu ---
(In reply to vries from comment #4)
> (In reply to H.J. Lu from comment #3)
> > Only build/genpreds in stage1 should be linked with libstdc++.so.6.
>
> Why?
Top level configure.ac has
[stage1_ldflags=
# In stag
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67092
--- Comment #6 from vries at gcc dot gnu.org ---
(In reply to H.J. Lu from comment #5)
> (In reply to vries from comment #4)
> > (In reply to H.J. Lu from comment #3)
> > > Only build/genpreds in stage1 should be linked with libstdc++.so.6.
> >
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67092
--- Comment #7 from vries at gcc dot gnu.org ---
(In reply to vries from comment #6)
> (In reply to H.J. Lu from comment #5)
> > (In reply to vries from comment #4)
> > > (In reply to H.J. Lu from comment #3)
> > > > Only build/genpreds in stage1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64164
--- Comment #49 from Gary Funck ---
(In reply to Alexandre Oliva from comment #48)
> The errors reported in comments 44, 45, 46, and 47 are fixed in the git
> branch aoliva/pr64164. I'm giving it all some more testing before posting
> an updated
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67092
--- Comment #8 from vries at gcc dot gnu.org ---
(In reply to vries from comment #7)
> I start to suspect it's related to this configure bit:
> ...
> --with-host-libstdcxx=-L/usr/local/tools/gcc-4.7.3/lib64 -static-libgcc
> -Wl,-Bstatic,-lstdc++,-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67093
--- Comment #3 from Andrew Pinski ---
And right before the quote you gave:
"An application that relies on such a feature or behavior cannot be assured to
be portable across conforming implementations."
So this might not be a full requirement of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67097
Bug ID: 67097
Summary: gcov-tool merge (can) crash when dir2 contains files
not in dir1
Product: gcc
Version: 5.2.0
Status: UNCONFIRMED
Severity: normal
22 matches
Mail list logo
