https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100241
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100241
--- Comment #9 from CVS Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:5fa4f982636e7e66eee6a9b45cc0939ae95b4659
commit r12-6164-g5fa4f982636e7e66eee6a9b45cc0939ae95b4659
Author: Andrew Pinski
Date: Sa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99766
--- Comment #11 from CVS Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:5fa4f982636e7e66eee6a9b45cc0939ae95b4659
commit r12-6164-g5fa4f982636e7e66eee6a9b45cc0939ae95b4659
Author: Andrew Pinski
Date: Sa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99787
--- Comment #3 from CVS Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:5fa4f982636e7e66eee6a9b45cc0939ae95b4659
commit r12-6164-g5fa4f982636e7e66eee6a9b45cc0939ae95b4659
Author: Andrew Pinski
Date: Sat
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100241
Andrew Pinski changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99766
Andrew Pinski changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100183
Andrew Pinski changed:
What|Removed |Added
Status|WAITING |NEW
See Also|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100183
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |MOVED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100755
Andrew Pinski changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100283
Andrew Pinski changed:
What|Removed |Added
CC||afernandez at odyhpc dot com
--- Commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84903
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84687
Andrew Pinski changed:
What|Removed |Added
CC||marcin.krotkiewski at gmail
dot co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90087
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=103828
Francois-Xavier Coudert changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88925
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67452
Andrew Pinski changed:
What|Removed |Added
Known to fail||5.1.0, 5.2.0
Summary|LTO ICE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66835
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67452
Andrew Pinski changed:
What|Removed |Added
CC||evstupac at gmail dot com
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43786
--- Comment #4 from Andrew Pinski ---
-fshort-enum or -funsigned-char/-fsigned-char might cause a smilar ICE.
-fshort-double was removed in GCC 6 by r6-6819 (aka PR 60410 ).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49697
Andrew Pinski changed:
What|Removed |Added
CC||pinskia at gcc dot gnu.org
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88643
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |MOVED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103882
--- Comment #6 from Jose Silva ---
Yes, noipa does help.
(In reply to Andrew Pinski from comment #3)
> Oh that is because there is some IPA Register allocation going on. Anyways
> this is still not a bug. You need to mark a0 as a clobber in the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103882
--- Comment #7 from Jakub Jelinek ---
(In reply to Jose Silva from comment #6)
> Yes, noipa does help.
>
> (In reply to Andrew Pinski from comment #3)
> > Oh that is because there is some IPA Register allocation going on. Anyways
> > this is st
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103882
--- Comment #8 from Jakub Jelinek ---
BTW, all this is documented in the gcc documentation (on Basic Asm and Extended
Asm).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93575
Gaius Mulley changed:
What|Removed |Added
CC||gaiusmod2 at gmail dot com
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103882
--- Comment #9 from Jose Silva ---
(In reply to Jakub Jelinek from comment #7)
> The compiler has no idea either (it has intentionally no idea what the
> inline asm does, it is a black box to the compiler), so that is why you need
> to specify i
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103885
Bug ID: 103885
Summary: ICE in capturing lambda for certain constexpr/auto
combination
Product: gcc
Version: 11.2.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103882
--- Comment #10 from Jakub Jelinek ---
That is just a total misunderstanding why the compiler needs to know (be told)
the observable side-effects of the inline asm. Interprocedural optimizations
are just one of the many reasons, much more impor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103879
--- Comment #4 from Jonathan Wakely ---
(In reply to Andrew Pinski from comment #1)
> clang rejects it also (with their libc++):
Libc++ doesn't support constexpr std::string, and I think it's missing some DRs
to std::variant as well. So I would
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103885
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |9.5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103885
Andrew Pinski changed:
What|Removed |Added
Keywords||needs-bisection
--- Comment #1 from And
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103882
Jose Silva changed:
What|Removed |Added
Resolution|INVALID |WONTFIX
--- Comment #11 from Jose Silva -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103886
Bug ID: 103886
Summary: Use 64-bit time_t on 32-bit glibc targets
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103882
Andreas Schwab changed:
What|Removed |Added
Resolution|WONTFIX |INVALID
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103882
--- Comment #12 from Jakub Jelinek ---
That is solely because you didn't write anything else in the function, try to
put some code around the inline asm and you'll see how it will misbehave even
with noipa attribute.
Your code is invalid as docu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103886
--- Comment #1 from Andrew Pinski ---
Is there anything to be done as the time_t is now defaults to 64bit on the
trunk of glibc?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57703
Andrew Pinski changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46820
Andrew Pinski changed:
What|Removed |Added
CC||mliska at suse dot cz
--- Comment #14 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57208
Bug 57208 depends on bug 57703, which changed state.
Bug 57703 Summary: Assembler function definition moved to a different ltrans
then call
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57703
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103886
--- Comment #2 from Janne Blomqvist ---
(In reply to Andrew Pinski from comment #1)
> Is there anything to be done as the time_t is now defaults to 64bit on the
> trunk of glibc?
AFAIU it's not the default, you need to explicitly opt-in by sett
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103886
--- Comment #3 from Andrew Pinski ---
(In reply to Janne Blomqvist from comment #2)
> (In reply to Andrew Pinski from comment #1)
> > Is there anything to be done as the time_t is now defaults to 64bit on the
> > trunk of glibc?
>
> AFAIU it's
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103390
--- Comment #5 from sandra at gcc dot gnu.org ---
Created attachment 52107
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52107&action=edit
-fdump-tree-original output from second test case
Well, this is nuts. Unmodified code is generatin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92385
Jason Merrill changed:
What|Removed |Added
CC||jason at gcc dot gnu.org
Assig
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103882
Jose Silva changed:
What|Removed |Added
Resolution|INVALID |WONTFIX
--- Comment #13 from Jose Silva -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50483
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102380
Bug 102380 depends on bug 50483, which changed state.
Bug 50483 Summary: lto turns visibility from HIDDEN to DEFAULT
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50483
What|Removed |Added
--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50483
--- Comment #4 from Andrew Pinski ---
Note I looked at both with and without the LTO plugin too to make sure it would
work in both cases.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103886
--- Comment #4 from Janne Blomqvist ---
(In reply to Andrew Pinski from comment #3)
> (In reply to Janne Blomqvist from comment #2)
> > (In reply to Andrew Pinski from comment #1)
> > > Is there anything to be done as the time_t is now defaults
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103887
Bug ID: 103887
Summary: -fsanitize=shift affects constness of an expression
Product: gcc
Version: 11.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Compo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99783
Stafford Horne changed:
What|Removed |Added
Resolution|--- |MOVED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103887
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79482
Andrew Pinski changed:
What|Removed |Added
CC||m...@mk-sys.cz
--- Comment #7 from Andre
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103887
--- Comment #2 from Michal Kubecek ---
(In reply to Andrew Pinski from comment #1)
> The problem is rather __builtin_constant_p not resolving to a constant. This
> is a dup of bug 79482.
There is a difference: your modified testcase fails to co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103887
--- Comment #3 from Andrew Pinski ---
(In reply to Michal Kubecek from comment #2)
> (In reply to Andrew Pinski from comment #1)
> > The problem is rather __builtin_constant_p not resolving to a constant. This
> > is a dup of bug 79482.
>
> The
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103887
--- Comment #4 from Michal Kubecek ---
It's probably even more complicated as
#define ASSERT_ON_COMPILE_SELECTOR_SIZE(expr) \
_Static_assert( \
__builtin_choose_expr(__builtin_constant_p(exp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103887
--- Comment #5 from Andrew Pinski ---
(In reply to Michal Kubecek from comment #4)
> As this is nicer than the original code, I guess I'll use it and hope it is
> not just a happy coincidence that it works.
It is not, see https://gcc.gnu.org/bu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56532
--- Comment #2 from Andrew Pinski ---
The only messages from valgrind I get these days are from IRA and LRA:
==15092== Command: ./cc1plus pr46984.C -O -fipa-cp -fno-early-inlining -flto
-quiet --param=ggc-min-expand=0 --param=ggc-min-heapsize=0 -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103888
Bug ID: 103888
Summary: ICE with global register definition after use
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Keywords: accepts-invalid, ice-on-invalid-code
Sever
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=29209
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103783
Fedor Chelnokov changed:
What|Removed |Added
CC||fchelnokov at gmail dot com
--- Comme
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101762
Andrew Pinski changed:
What|Removed |Added
Summary|ICE in ix86_push_argument, |ICE with "Every subscript
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=33193
Andrew Pinski changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |pinskia at gcc dot
gnu.org
62 matches
Mail list logo