https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91947
--- Comment #14 from Jonathan Wakely ---
I think this is simpler and less likely to cause problems:
# This header is not installed, it's only used to build libstdc++ itself.
${host_builddir}/largefile-config.h: ${CONFIG_HEADER}
@rm -f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92474
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93341
rsandifo at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93341
--- Comment #7 from CVS Commits ---
The master branch has been updated by Richard Sandiford :
https://gcc.gnu.org/g:2214053f9d9cdf66a4f3a657dbae43d293fd0387
commit r10-6176-g2214053f9d9cdf66a4f3a657dbae43d293fd0387
Author: Richard Sandiford
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93178
--- Comment #3 from Segher Boessenkool ---
The code at
https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=gcc/config/rs6000/rs6000.c;h=fc36bb6714b2a4c922e903e2ebe333c6bdaeefcd;hb=HEAD#l9229
does not treat this case specially, but it should.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92538
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
URL|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93399
--- Comment #4 from Andrew Pinski ---
dwarf2out.c:27492 or so
in dwarf2out_var_location.
I think ...
Here is a reduced testcase without any headers:
extern __inline __attribute__ ((__always_inline__)) __attribute__
((__gnu_inline__)) char *
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92463
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91824
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91873
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91882
Andrew Pinski changed:
What|Removed |Added
CC||pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91838
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91882
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93399
Andrew Pinski changed:
What|Removed |Added
Target|x86_64-*-* |
--- Comment #3 from Andrew Pinski ---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91838
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #116 from dave.anglin at bell dot net ---
On 2020-01-22 10:30 p.m., peter.bisroev at groundlabs dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
>
> --- Comment #115 from Peter Bisroev ---
> Hi Dave,
>
> (In reply
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93400
Richard Biener changed:
What|Removed |Added
Keywords||ice-on-valid-code
Target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93369
--- Comment #6 from Martin Liška ---
(In reply to Segher Boessenkool from comment #5)
> You can also shorten the sha, say, g:28307164dfed here.
Yes, but I was asked by Jakub to always use:
git gcc-descr --full $hash
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91916
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91810
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93369
Segher Boessenkool changed:
What|Removed |Added
CC||segher at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91120
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91139
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
efault-pie
--enable-default-ssp --enable-cet=auto --disable-boostrap
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 10.0.1 20200123 (experimental) (GCC)
```
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91128
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93345
--- Comment #4 from David Binderman ---
I also see this error when compiling Fedora package csdiff.
Reduced test case available on request.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91138
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93324
--- Comment #5 from gcc-bugs at marehr dot dialup.fu-berlin.de ---
Thank you! I can confirm it being fixed <3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91146
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93399
--- Comment #2 from Marek Polacek ---
The error I see is:
/tmp/ccmVatwF.s: Assembler messages:
/tmp/ccmVatwF.s:90: Error: invalid character (0xa) in mnemonic
/tmp/ccmVatwF.s:92: Error: unassigned file number 2
/tmp/ccmVatwF.s:92: Error: junk at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93399
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93384
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93387
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=2020
--- Comment #7 from CVS Commits ---
The master branch has been updated by Andrew Stubbs :
https://gcc.gnu.org/g:14e5e74698b98f4cbe398cb989dfa27765cbca6e
commit r10-6173-g14e5e74698b98f4cbe398cb989dfa27765cbca6e
Author: Andrew Stubbs
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93057
Martin Liška changed:
What|Removed |Added
Status|ASSIGNED|NEW
Assignee|marxin at gcc dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93393
--- Comment #5 from Segher Boessenkool ---
It is a backend issue that we cannot solve properly without solving much bigger
generic problems first. See the BoF at last year’s cauldron. Without fixing
that first, doing signaling floats regresses
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93346
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91123
Bug 91123 depends on bug 93354, which changed state.
Bug 93354 Summary: [10 Regression] Bogus remove of redundant store
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93354
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93399
Bug ID: 93399
Summary: Annotate assembler option failure
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93354
Richard Biener changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93381
--- Comment #5 from CVS Commits ---
The master branch has been updated by Richard Guenther :
https://gcc.gnu.org/g:f5ee5d05f367d6221b76f7a3ef7dad96605dbf04
commit r10-6172-gf5ee5d05f367d6221b76f7a3ef7dad96605dbf04
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91947
--- Comment #13 from Eric Botcazou ---
> It's done the same way as we've always created the
> ${host_builddir}/c++config.h target, so I'm not sure why one is racy and the
> other isn't.
I didn't mean that the first one was not racy though ;-)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93346
--- Comment #6 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:9592f639ff4655203f1cffb7c6752696e2721fb0
commit r10-6171-g9592f639ff4655203f1cffb7c6752696e2721fb0
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84919
--- Comment #19 from CVS Commits ---
The master branch has been updated by Martin Sebor :
https://gcc.gnu.org/g:8a990ffafaaa18981c6e91d4ed88f05ed74c5f3f
commit r10-6170-g8a990ffafaaa18981c6e91d4ed88f05ed74c5f3f
Author: Martin Sebor
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91947
Jonathan Wakely changed:
What|Removed |Added
Status|RESOLVED|ASSIGNED
Resolution|FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93398
--- Comment #7 from Martin Liška ---
Created attachment 47697
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47697=edit
GCOV dump diff
There's still some difference, but rather small.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93398
Martin Liška changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92152
--- Comment #11 from rguenther at suse dot de ---
On Wed, 22 Jan 2020, hubicka at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92152
>
> --- Comment #10 from Jan Hubicka ---
> Concerning:
> > Honza, the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93124
rsandifo at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90348
--- Comment #16 from Richard Biener ---
Even before IVOPTs we have an access to in[] "after" the clobber. I think the
fact that there are multiple instances of in is not well represented and
for the testcase at hand jump-threading essentially
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91947
--- Comment #11 from Jonathan Wakely ---
It's done the same way as we've always created the ${host_builddir}/c++config.h
target, so I'm not sure why one is racy and the other isn't.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93398
--- Comment #5 from Martin Liška ---
And there's also a difference in TOPN counters:
diff -u a b
--- a 2020-01-23 10:30:56.527098370 +0100
+++ b 2020-01-23 10:30:42.035189528 +0100
@@ -1,21 +1,21 @@
-== Stats for after ==
+== Stats for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93398
--- Comment #4 from Martin Liška ---
(In reply to Jakub Jelinek from comment #2)
> Couldn't e.g. address space randomization of the instrumented binaries
> (compiler itself) matter?
I must confirm that the machine where I run it has ASLR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93124
--- Comment #3 from CVS Commits ---
The master branch has been updated by Richard Sandiford :
https://gcc.gnu.org/g:ccb68179642cf7ba5ee05a0d8571a95d0145e3a2
commit r10-6166-gccb68179642cf7ba5ee05a0d8571a95d0145e3a2
Author: Richard Sandiford
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92692
Richard Biener changed:
What|Removed |Added
CC||rguenth at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93398
--- Comment #3 from Richard Biener ---
(In reply to Jakub Jelinek from comment #2)
> Couldn't e.g. address space randomization of the instrumented binaries
> (compiler itself) matter?
I bet some hash-tables could end up with different access
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93397
Richard Biener changed:
What|Removed |Added
Priority|P3 |P1
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93395
Richard Biener changed:
What|Removed |Added
Keywords||missed-optimization
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93398
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93393
Richard Biener changed:
What|Removed |Added
Component|other |testsuite
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93391
Richard Biener changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93398
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
101 - 162 of 162 matches
Mail list logo
