https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95146
Bug ID: 95146
Summary: gfortran -cpp – leading spaces before '#'
preprocessing directive not handled
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: no
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95133
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
Priority|P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95134
Richard Biener changed:
What|Removed |Added
Resolution|--- |WONTFIX
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95146
--- Comment #1 from Tobias Burnus ---
This seems to be a side effect of using
-traditional
in gfortran see PR 28662 for moving to no traditional.
Also gcc -E -traditional shows this behavior of just echoing the strings.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95140
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |10.2
Priority|P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95046
--- Comment #11 from CVS Commits ---
The master branch has been updated by Uros Bizjak :
https://gcc.gnu.org/g:f4356120ba88c083dd5987376aab7590dd1e0e13
commit r11-409-gf4356120ba88c083dd5987376aab7590dd1e0e13
Author: Uros Bizjak
Date: Fri Ma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95143
Richard Biener changed:
What|Removed |Added
Resolution|--- |FIXED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95141
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
Last reconfir
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95145
Richard Biener changed:
What|Removed |Added
Keywords||error-recovery,
|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95146
--- Comment #2 from Andrew Pinski ---
Pre ANSI/ISO C (aka K&R C), preprocessor were true preprocessor and always
required # in the first column.
I think meson should be fixed really to work rather than working around the
issue in gfortran.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95146
--- Comment #3 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #2)
> Pre ANSI/ISO C (aka K&R C), preprocessor were true preprocessor and always
> required # in the first column.
>
> I think meson should be fixed really to work rat
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95147
Richard Biener changed:
What|Removed |Added
CC||hjl.tools at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95146
Tobias Burnus changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95147
Bug ID: 95147
Summary: Bootstrap fails with GCC 4.8 host compiler
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95147
--- Comment #1 from Richard Biener ---
--disable-cet seems to be a workaround, it looks like the configury fails to
check for host compiler support (or alternatively --disable-cet should be the
default for stage1?)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95046
--- Comment #12 from CVS Commits ---
The master branch has been updated by Uros Bizjak :
https://gcc.gnu.org/g:f8b0665445bee8673b62c0a40ae257fe8c75a9b6
commit r11-410-gf8b0665445bee8673b62c0a40ae257fe8c75a9b6
Author: Uros Bizjak
Date: Fri Ma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53947
Bug 53947 depends on bug 92611, which changed state.
Bug 92611 Summary: auto vectorization failed for type promotation
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92611
What|Removed |Added
-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92492
Bug 92492 depends on bug 92611, which changed state.
Bug 92611 Summary: auto vectorization failed for type promotation
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92611
What|Removed |Added
-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92611
Hongtao.liu changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92658
--- Comment #13 from Hongtao.liu ---
*** Bug 92611 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95141
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95148
Bug ID: 95148
Summary: -Wtype-limits always-false warning triggered despite
comparison being avoided
Product: gcc
Version: 10.1.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95137
Martin Liška changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94799
Volker Reichelt changed:
What|Removed |Added
CC||reichelt at gcc dot gnu.org
--- Commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94635
--- Comment #5 from CVS Commits ---
The master branch has been updated by Tobias Burnus :
https://gcc.gnu.org/g:9f0f7da9aa98eec28b4e5e34ade0aa0028df161d
commit r11-412-g9f0f7da9aa98eec28b4e5e34ade0aa0028df161d
Author: Tobias Burnus
Date: Fri
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95133
--- Comment #5 from CVS Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:aaf1ee48316f9b414b11c17e298198925d816595
commit r11-414-gaaf1ee48316f9b414b11c17e298198925d816595
Author: Richard Biener
Date: F
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95133
Richard Biener changed:
What|Removed |Added
Known to work||11.0
Summary|[8/9/10/11 Regr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95131
--- Comment #3 from Trass3r ---
Well sure but most existing codebases won't be ported to modules because of the
effort while enabling pch is now straightforward with latest CMake.
These conformance issues have also been identified in
https://rev
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95149
Bug ID: 95149
Summary: lex.c:1729:8: warning: result of comparison against a
string literal is unspecified (use an explicit string
comparison function instead) [-Wstring-compare]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95149
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95149
--- Comment #2 from Jakub Jelinek ---
With string merging even "foobar" + 3 == "bar" (or not, depending on alignment
decision, how hard does the linker optimize etc.). For static vars only if
-fmerge-all-constants and the var would be const and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95082
--- Comment #4 from Segher Boessenkool ---
But this PR has more info, so I'll close the older one as dup, instead.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95070
Segher Boessenkool changed:
What|Removed |Added
CC||segher at gcc dot gnu.org
R
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95082
--- Comment #3 from Segher Boessenkool ---
*** Bug 95070 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95149
--- Comment #3 from Andrew Pinski ---
The code here is correct. In that the warning might be valid for normal code
but the comparasion it is making is valid one.
Mainly because we do:
/* Restore backslash followed by newline. */
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94307
--- Comment #9 from Martin Liška ---
Any update on this Kees?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94910
Martin Liška changed:
What|Removed |Added
Status|ASSIGNED|WAITING
--- Comment #2 from Martin Liška
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95150
Bug ID: 95150
Summary: Some offloaded programs crash with openmp
Product: gcc
Version: 10.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libgom
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92260
--- Comment #7 from CVS Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:584a3c080bbd6e64131fa53771c7424bcf9d21fa
commit r11-418-g584a3c080bbd6e64131fa53771c7424bcf9d21fa
Author: Richard Biener
Date: F
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94496
--- Comment #3 from Witold Baryluk ---
Also about 'nothrow' and Errors.
I would really welcome a flag to compiler that simply terminates all threads
immidetly any Error is thrown at throw location. They aren't really
recoverable. The only option
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67300
Tobias Burnus changed:
What|Removed |Added
CC||burnus at gcc dot gnu.org
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95151
Bug ID: 95151
Summary: Add cmpmemM pattern for -minline-all-stringops
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tar
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94799
--- Comment #10 from Marek Polacek ---
I see :(. I'll take a look, thanks for noticing.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95152
Bug ID: 95152
Summary: internal compiler error: in get_or_create_mem_ref, at
analyzer/region-model.cc:6938
Product: gcc
Version: 10.1.0
Status: UNCONFIRMED
Seve
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95147
H.J. Lu changed:
What|Removed |Added
Last reconfirmed||2020-05-15
Assignee|unassigned at gc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95147
H.J. Lu changed:
What|Removed |Added
URL||https://gcc.gnu.org/piperma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95152
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95153
Bug ID: 95153
Summary: Arrays of 'const void *' should not be copyable
Product: gcc
Version: 10.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95132
Patrick Palka changed:
What|Removed |Added
CC||ppalka at gcc dot gnu.org
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95153
--- Comment #1 from Alisdair Meredith ---
Forgot to add this is specific to -std=c++20 too.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94535
--- Comment #13 from Alisdair Meredith ---
As this has shipped for two releases now (gcc9 and 10) I recommend closing as
Works As Designed, citing C standard paper N2322 as reason for the change.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95150
--- Comment #1 from Tobias Burnus ---
* You compilation uses "-O0" – I do not know whether that's intended.
* I did not see any timeout message although it did take a while to run
with offloading. (See timing results below.)
I wonder what ca
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95100
Patrick Palka changed:
What|Removed |Added
CC||ppalka at gcc dot gnu.org
--- Comment #1
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: sch...@linux-m68k.org
Target Milestone: ---
Target: ia64-*-*
spawn -ignore SIGHUP
/usr/local/gcc/gcc-20200515/Build/gcc/testsuite/g++3/../../xg++
-B
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94690
--- Comment #11 from CVS Commits ---
The master branch has been updated by Tobias Burnus :
https://gcc.gnu.org/g:0ec52417fd9b3bef5227cdc9a18ff4f0247b0ea4
commit r11-421-g0ec52417fd9b3bef5227cdc9a18ff4f0247b0ea4
Author: Tobias Burnus
Date: Fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83028
Rafael Avila de Espindola changed:
What|Removed |Added
CC||rafael at espindo dot la
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95154
--- Comment #1 from Andreas Schwab ---
The problem is that when output_constant processes a FDESC_EXPR it calls
ASM_OUTPUT_FDESC, which doesn't do weak processing (it doesn't call
assemble_external).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95150
--- Comment #2 from Chinoune ---
Created attachment 48546
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48546&action=edit
debug ouput
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95150
--- Comment #3 from Chinoune ---
(In reply to Tobias Burnus from comment #1)
> * You compilation uses "-O0" – I do not know whether that's intended.
I didn't set any optimization flag, maybe the compiler default to "-O0".
>
> * I did not see a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95147
H.J. Lu changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95147
--- Comment #3 from CVS Commits ---
The master branch has been updated by H.J. Lu :
https://gcc.gnu.org/g:4c1a5d8b71e29b71e0bc1004480c12c5fc427cb7
commit r11-422-g4c1a5d8b71e29b71e0bc1004480c12c5fc427cb7
Author: H.J. Lu
Date: Fri May 15 09:0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94910
--- Comment #3 from Rafael Avila de Espindola ---
Yes, our build bots use podman, so you can reproduce with:
$ git clone https://github.com/scylladb/seastar
$ cd seastar
$ podman run -v $PWD:$PWD:z -w $PWD -it
docker.io/scylladb/scylla-toolchain
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95153
TC changed:
What|Removed |Added
CC||rs2740 at gmail dot com
--- Comment #2 from TC ---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93286
--- Comment #6 from CVS Commits ---
The master branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:cda6396a1b6e6bba2a3b0847931567c3458f2184
commit r11-423-gcda6396a1b6e6bba2a3b0847931567c3458f2184
Author: Jason Merrill
Date: Fri
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90996
--- Comment #6 from CVS Commits ---
The master branch has been updated by Patrick Palka :
https://gcc.gnu.org/g:289fbbe75f6d1c69605fcfde769ac46944c14a4a
commit r11-424-g289fbbe75f6d1c69605fcfde769ac46944c14a4a
Author: Patrick Palka
Date: Fri
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87210
--- Comment #6 from qinzhao at gcc dot gnu.org ---
So, based on the previous discussion on the LLVM option
-ftrivial-auto-var-init=[uninitialized|pattern|zero]
we can see:
-ftrivial-auto-var-init=pattern
might not be a good idea due to the fol
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95155
Bug ID: 95155
Summary: d: wrong vtable offset in virtual function call
Product: gcc
Version: 9.3.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: d
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95156
Bug ID: 95156
Summary: -Wtautological-compare warns in C but not C++
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95157
Bug ID: 95157
Summary: Missing -Wtautological-compare warning
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95061
--- Comment #7 from CVS Commits ---
The master branch has been updated by Ian Lance Taylor :
https://gcc.gnu.org/g:e478cacb62f116d2c8efdabc4b51e6d2d7041aae
commit r11-432-ge478cacb62f116d2c8efdabc4b51e6d2d7041aae
Author: Ian Lance Taylor
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95137
--- Comment #4 from Rafael Avila de Espindola ---
Created attachment 48547
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48547&action=edit
testcase
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95137
--- Comment #5 from Rafael Avila de Espindola ---
With a seastar patched for c++ 20 (mostly dropping a few experimental/ from
includes and experimental:: from names), the following is all that is needed:
#include
#include
using namespace seast
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95100
--- Comment #2 from rhalbersma ---
OK, so the rewriting rules [range.adaptors]/4, that make views::xxx(R)
equivalent to R | views::xxx, do not allow to rewrite the expression equivalent
xxx_view{R} as R | xxx_view? That would be rather finicky, p
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95158
Bug ID: 95158
Summary: Templates + Diamond Inheritance + Final = Pure Virtual
Function Call
Product: gcc
Version: 10.1.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95155
--- Comment #1 from Iain Buclaw ---
Looks like fix was in r10-7280, taken from the upstream backport in
https://github.com/dlang/dmd/pull/10913
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=10138
Martin Sebor changed:
What|Removed |Added
Keywords||patch
Last reconfirmed|2008-03-30 20:45
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57943
--- Comment #3 from CVS Commits ---
The master branch has been updated by Patrick Palka :
https://gcc.gnu.org/g:115232b778943be075fc4df991e03d9387563114
commit r11-434-g115232b778943be075fc4df991e03d9387563114
Author: Patrick Palka
Date: Fri
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57943
Patrick Palka changed:
What|Removed |Added
Target Milestone|--- |11.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95156
Martin Sebor changed:
What|Removed |Added
Version|unknown |11.0
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=15880
Martin Sebor changed:
What|Removed |Added
Known to work||4.1.0
Resolution|DUPLICATE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95159
Bug ID: 95159
Summary: ICE on aggregate template parameter with empty angle
brackets
Product: gcc
Version: 10.1.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95159
--- Comment #1 from Paco Arjonilla ---
GCC 10.1, not GCC 10.0.1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95160
Bug ID: 95160
Summary: Explicit specialization in non-namespace scope bug
Product: gcc
Version: 10.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Componen
83 matches
Mail list logo