https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53155
--- Comment #6 from Marc Glisse ---
(In reply to Andrew Pinski from comment #5)
> Hmm, Did something change in make?
It looks like make now splits -j from other flags in MFLAGS, -wkj becomes -kw
-j, so the old filters probably work now...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102054
--- Comment #2 from Kewen Lin ---
Yet another reduced test case from 526.blender_r.
#include
typedef struct QMCSampler {
struct QMCSampler *next, *prev;
int type;
int tot;
int used;
double *samp2d;
double offs[1][2];
} QMCSampler;
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50891
--- Comment #4 from Andrew Pinski ---
Hmm, was this solve by r0-123608-g7894bc6be052 ?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50497
--- Comment #4 from Andrew Pinski ---
I should note that -gpubnames was added with r0-117471 for GCC 4.8.0.
And -ggnu-pubnames was added with r0-125994 for 4.9.0.
You can use those options if you want pubnames.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50497
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |WONTFIX
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102145
--- Comment #11 from Rimvydas (RJ) ---
(In reply to Steve Kargl from comment #10)
> Yes, I know -std=legacy implies -fallow-argument-mismatch. The
> option degrades an ERROR to a WARNING. That is all it does.
> With -std=legacy, gfortran is a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102301
--- Comment #2 from 康桓瑋 ---
(In reply to Andrew Pinski from comment #1)
> Even LLVM's libc++ does not support this ...
I think you are right, but I want to know what libstdc++ thinks about this
issue.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102301
--- Comment #1 from Andrew Pinski ---
Even LLVM's libc++ does not support this ...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102301
Bug ID: 102301
Summary: make_from_tuple can not work with subrange
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libst
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102294
Andrew Pinski changed:
What|Removed |Added
Component|middle-end |target
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102294
--- Comment #10 from Hongtao.liu ---
(In reply to Bart Van Assche from comment #9)
> Hmm ... isn't movups a floating-point instruction? I want to avoid floating
> point instructions since my understanding is that it is not allowed to use
> these
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102294
--- Comment #9 from Bart Van Assche ---
Hmm ... isn't movups a floating-point instruction? I want to avoid floating
point instructions since my understanding is that it is not allowed to use
these in kernel code. See e.g.
https://stackoverflow.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102300
Andrew Pinski changed:
What|Removed |Added
Keywords||rejects-valid
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102300
Bug ID: 102300
Summary: Qualified name in class template
Product: gcc
Version: 11.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102294
Hongtao.liu changed:
What|Removed |Added
CC||crazylht at gmail dot com
--- Comment #8
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102294
--- Comment #7 from Bart Van Assche ---
Initializing small data structures via structure assignment is a common
approach in the Linux kernel.
This is the code gcc generates with the no-sse option applied:
(gdb) disas bio_init3
Dump of assemble
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102145
--- Comment #10 from Steve Kargl ---
On Sun, Sep 12, 2021 at 11:40:31PM +, rimvydas.jas at gmail dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102145
> > -fallow-argument-mismatch was added to allow users,
> > who refuse to f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96184
Jason Merrill changed:
What|Removed |Added
Assignee|jason at gcc dot gnu.org |unassigned at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96184
--- Comment #5 from Jason Merrill ---
Created attachment 51446
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51446&action=edit
fix that causes regressions
This patch fixes this testcase, but regresses the testcases from PR91506 and
PR4178
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102294
--- Comment #6 from Andrew Pinski ---
This is literally just measuring memset times of a small structure.
-mtune=intel changes the timings too.
Doing -mstringop-strategy=libcall also changes the timing to the point where
they are about the same
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102294
--- Comment #5 from Bart Van Assche ---
Please note that bio_init3() does not use atomic_set() but ATOMIC_INIT(). The
definition of ATOMIC_INIT() is as follows:
#define ATOMIC_INIT(v) (atomic_t){.counter = (v)}
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102294
--- Comment #4 from Andrew Pinski ---
First atomic_set has an volatile store in it which messes things up a lot.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102294
--- Comment #3 from Bart Van Assche ---
Thanks for the quick feedback. I have modified the test program and added
target("no-sse") to the bio_init[123]() functions. With that change applied the
results are as follows:
$ gcc -O2 -o bio_init bio_
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102294
Bart Van Assche changed:
What|Removed |Added
Attachment #51444|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102292
--- Comment #2 from Eason Lai ---
sorry, I'm not sure whether this is a linker issue or not. Only thing I know is
enabling or disabling LTO makes the result different.
I can do more experiments to provide information if any suggestions. Thank y
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91103
--- Comment #10 from Hongtao.liu ---
(In reply to Peter Cordes from comment #9)
> Thanks for implementing my idea :)
>
> (In reply to Hongtao.liu from comment #6)
> > For elements located above 128bits, it seems always better(?) to use
> > valig
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87555
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102145
--- Comment #9 from Rimvydas (RJ) ---
(In reply to Steve Kargl from comment #8)
> Yes, it should behave like -pedantic-errors.
Actually no, -pedantic is equivalent to -Wpedantic, while -pedantic-errors is
-Werror=pedantic. Rest is interpretatio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101045
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88578
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102295
--- Comment #1 from Andrew Pinski ---
Note the C front-end has add_flexible_array_elts_to_size in c/c-decl.c which
sets the DECL_SIZE to be correct.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102296
Andrew Pinski changed:
What|Removed |Added
Summary|ELF symbol sizes for|ELF symbol sizes for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102299
Bug ID: 102299
Summary: ELF symbol sizes for variable-length objects are too
small (openbsd)
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Keywords: wrong-cod
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102298
Bug ID: 102298
Summary: ELF symbol sizes for variable-length objects are too
small (mips)
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Keywords: wrong-code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102297
Bug ID: 102297
Summary: symbol sizes for variable-length objects are broken
(mcore)
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Keywords: wrong-code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102296
Bug ID: 102296
Summary: ELF symbol sizes for variable-length objects are
broken
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Keywords: wrong-code
S
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63373
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102145
--- Comment #8 from Steve Kargl ---
On Sun, Sep 12, 2021 at 07:34:17PM +, rimvydas.jas at gmail dot com wrote:
>
> > No, it is not. The -fallow-argument-match option was given to
> > user to allow them to compile their broken code. It was
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102295
Bug ID: 102295
Summary: ELF symbol sizes for variable-length objects are too
small (C++)
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Keywords: wrong-code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57295
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |5.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52124
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2021-09-12
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52124
Andrew Pinski changed:
What|Removed |Added
CC||ettl.martin at gmx dot de
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62311
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102294
--- Comment #1 from Andrew Pinski ---
Note the Linux kernel compiles with -mno-sse where the results are hugely
difference than what can be done in the usespace where SSE can provide a speed
boost.
The easiest way to test this is to use -m32 -m
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102294
Bug ID: 102294
Summary: structure assignment slower than memberwise
initialization
Product: gcc
Version: 11.2.1
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53155
--- Comment #5 from Andrew Pinski ---
Hmm:
apinski@xeond:~/src/upstream-gcc/t$ make -j
make plouf
make[1]: Entering directory '/bajas/pinskia/src/upstream-gcc/t'
echo -w -j "-j"
-w -j -j
make[1]: Leaving directory '/bajas/pinskia/src/upst
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60954
Andrew Pinski changed:
What|Removed |Added
Version|unknown |12.0
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59532
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57812
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53091
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |8.0
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24201
Andrew Pinski changed:
What|Removed |Added
Keywords||missed-optimization
Last reconfirmed|2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49477
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54654
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |FIXED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102293
--- Comment #2 from andysem at mail dot ru ---
The code compiles if -std=c++03 is replaced with e.g. -std=c++11.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102293
--- Comment #1 from andysem at mail dot ru ---
I forgot to mention that the same code compiles successfully with gcc 9.4.0.
And here is the output from gcc 11.1.0:
In file included from ./boost/assert.hpp:58,
from
./boost/xpres
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102293
Bug ID: 102293
Summary: [10 regression] ICE when compiling Boost.Xpressive (in
value_dependent_expression_p, at cp/pt.c:26730)
Product: gcc
Version: 10.3.0
Status: UNCON
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65396
--- Comment #9 from Andrew Pinski ---
Another simplified testcase:
template void f();
template void f() {}
int main() { f(); }
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65396
Andrew Pinski changed:
What|Removed |Added
CC||sp2danny at gmail dot com
--- Comment #8
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87279
Andrew Pinski changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53751
--- Comment #4 from Andrew Pinski ---
I think this has been fixed with the patches which change the name based on the
output file name instead of the first input.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65454
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Keywords||rejects-valid
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102145
--- Comment #7 from Rimvydas (RJ) ---
(In reply to kargl from comment #6)
> Well, that's what it should do! Argument mismatch has never
> been permitted by any Fortran standard. So, PEDANTICALLY
> speaking it is an error to allow.
Pedantically
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102145
--- Comment #6 from kargl at gcc dot gnu.org ---
(In reply to Rimvydas (RJ) from comment #4)
> (In reply to ripero84 from comment #0)
> > In the presence of -pedantic, -fallow-argument-mismatch fails to degrade the
> > mismatch errors to warnings
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101918
Rimvydas (RJ) changed:
What|Removed |Added
Attachment #51398|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102145
--- Comment #5 from Rimvydas (RJ) ---
Created attachment 51441
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51441&action=edit
old WIP for arg mismatch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102145
Rimvydas (RJ) changed:
What|Removed |Added
CC||rimvydas.jas at gmail dot com
--- Comme
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82877
Johel Ernesto Guerrero Peña changed:
What|Removed |Added
CC||johelegp at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85130
--- Comment #6 from anlauf at gcc dot gnu.org ---
Submitted: https://gcc.gnu.org/pipermail/fortran/2021-September/056500.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49761
Andrew Pinski changed:
What|Removed |Added
Keywords||missed-optimization
Severity|m
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102185
Iain Buclaw changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102185
--- Comment #2 from CVS Commits ---
The releases/gcc-11 branch has been updated by Iain Buclaw
:
https://gcc.gnu.org/g:09a2049123e242aaf8a4bbfa8eb3ce92901b6f4e
commit r11-8982-g09a2049123e242aaf8a4bbfa8eb3ce92901b6f4e
Author: Iain Buclaw
Date
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102185
--- Comment #1 from CVS Commits ---
The master branch has been updated by Iain Buclaw :
https://gcc.gnu.org/g:53a4def0dc1aac39d592a0d20e9ec16e8b5574ac
commit r12-3465-g53a4def0dc1aac39d592a0d20e9ec16e8b5574ac
Author: Iain Buclaw
Date: Fri S
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19336
--- Comment #5 from dave.anglin at bell dot net ---
Appears to require implementation of __lshrti3, __ashlti3, __ashrti3, __multi3,
__udivti3, __umodti3, etc.
Various soft float routines are needed to perform conversions to/from ti mode.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101970
Eric Botcazou changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |ebotcazou at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101970
Eric Botcazou changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49664
--- Comment #3 from Andrew Pinski ---
Created attachment 51440
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51440&action=edit
Patch which at least builds correctly in lto-plugin
The previous patch I had a typo where I had put oncall inst
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49664
Andrew Pinski changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |pinskia at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85335
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60548
Eric Gallager changed:
What|Removed |Added
CC||ctice at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49563
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92435
Eric Gallager changed:
What|Removed |Added
CC||dmalcolm at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=34115
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102285
--- Comment #6 from David Binderman ---
(In reply to qinzhao from comment #5)
> with the latest GCC, for all the 42647 c files under gcc/testsuite, with -c
> -g -O2 -Wall -ftrivial-auto-var-init=zero, there is only one failure:
> /home/opc/Inst
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53746
Andrew Pinski changed:
What|Removed |Added
Keywords||lto, wrong-code
Component|lto
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61296
Andrew Pinski changed:
What|Removed |Added
CC||drepper.fsp at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54167
Andrew Pinski changed:
What|Removed |Added
Known to work||4.4.7, 4.9.0
Target|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25470
Andrew Pinski changed:
What|Removed |Added
CC||jrt at worldlinc dot net
--- Comment #27
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53384
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
88 matches
Mail list logo