https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84463
--- Comment #4 from Jakub Jelinek ---
Author: jakub
Date: Wed Apr 18 06:57:45 2018
New Revision: 259458
URL: https://gcc.gnu.org/viewcvs?rev=259458&root=gcc&view=rev
Log:
PR c++/84463
* typeck.c (cp_build_addr_expr_1): Move handl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80290
--- Comment #23 from Andrew Jeffery ---
> The patch is in. I suppose there's still room for improvement, but this was
> as far as I could get for now.
Thanks for your effort! I'll take it for a test drive when I get a moment, we
hit this case
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71959
Tom de Vries changed:
What|Removed |Added
CC||vries at gcc dot gnu.org
Summa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82686
Eric Gallager changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80290
Alexandre Oliva changed:
What|Removed |Added
Assignee|aoliva at gcc dot gnu.org |unassigned at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80290
--- Comment #21 from Alexandre Oliva ---
Author: aoliva
Date: Wed Apr 18 05:17:26 2018
New Revision: 259457
URL: https://gcc.gnu.org/viewcvs?rev=259457&root=gcc&view=rev
Log:
[PR c++/80290] recycle tinst garbage sooner
tinst_level objects are c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35363
--- Comment #8 from Andrew Pinski ---
There are two issues here, one is SLOW_BYTE_ACCESS and the second is the
lowering of bit-fields. I am going to fix the lower part for GCC 9. The
SLOW_BTYE_ACCESS was being looked at by someone else in the r
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85437
Alexandre Oliva changed:
What|Removed |Added
CC||aoliva at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82037
--- Comment #10 from Dennis Clarke ---
Can we close this as a non-issue?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82686
--- Comment #16 from Dennis Clarke ---
Can we close this as a non-issue?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85440
--- Comment #2 from Dennis Clarke ---
Thank you very much Sir!
So then .. where is this gcc 8 that you speak of ? Still just a
nightly test release or is there an actual tarball hidden away?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84442
--- Comment #5 from dave.anglin at bell dot net ---
On 2018-04-17 10:21 AM, redi at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84442
>
> --- Comment #4 from Jonathan Wakely ---
> Dave, does the patch in comment 3 fix th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85444
--- Comment #1 from Will Hawkins ---
Created attachment 43971
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43971&action=edit
Example that triggers the newly added warning when compiled with -Wpedantic
Example that triggers the newly adde
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85444
Bug ID: 85444
Summary: asm specifier on typedef silently ignored
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85429
--- Comment #1 from Ian Lance Taylor ---
Does the SPARC Solaris assembler support a syntax like
.section ".go.buildid",#exclude
? That's what gas seems to support for compatibility.
Does that syntax work for x86?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85442
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85440
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85443
Bug ID: 85443
Summary: internal compiler error: Segmentation fault
Product: gcc
Version: 5.5.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84637
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63426
Bug 63426 depends on bug 84637, which changed state.
Bug 84637 Summary: gcc/dbxout.c:684:14: runtime error: negation of
-9223372036854775808 cannot be represented in type 'long int'; cast to an
unsigned type to negate this value to itself
https:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84637
--- Comment #4 from Jakub Jelinek ---
Author: jakub
Date: Tue Apr 17 22:18:47 2018
New Revision: 259451
URL: https://gcc.gnu.org/viewcvs?rev=259451&root=gcc&view=rev
Log:
PR debug/84637
* dbxout.c (dbxout_int): Perform negation i
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85394
seurer at gcc dot gnu.org changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |seurer at gcc dot
gnu.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84856
--- Comment #10 from Jim Wilson ---
Author: wilson
Date: Tue Apr 17 21:41:07 2018
New Revision: 259449
URL: https://gcc.gnu.org/viewcvs?rev=259449&root=gcc&view=rev
Log:
RISC-V: Fix 32-bit stack pointer alignment problem.
gcc/
P
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85431
--- Comment #2 from Jakub Jelinek ---
Author: jakub
Date: Tue Apr 17 21:38:45 2018
New Revision: 259448
URL: https://gcc.gnu.org/viewcvs?rev=259448&root=gcc&view=rev
Log:
PR rtl-optimization/85431
* dse.c (record_store): Ignore z
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85431
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63426
Bug 63426 depends on bug 85431, which changed state.
Bug 85431 Summary: UBSAN: ../../gcc/dse.c:303:15: runtime error: shift exponent
64 is too large for 64-bit type 'long unsigned int'
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85431
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85442
Bug ID: 85442
Summary: [8 Regression] cxx11-ios_failure.lo build fails for
microblaze
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
P
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84640
Thomas Koenig changed:
What|Removed |Added
Status|NEW |ASSIGNED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85434
Wilco changed:
What|Removed |Added
CC||wilco at gcc dot gnu.org
--- Comment #4 from Wil
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85326
--- Comment #8 from Jakub Jelinek ---
Author: jakub
Date: Tue Apr 17 20:43:49 2018
New Revision: 259447
URL: https://gcc.gnu.org/viewcvs?rev=259447&root=gcc&view=rev
Log:
PR testsuite/85326
* g++.dg/other/pr81422.C: Require effec
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85436
Peter Bergner changed:
What|Removed |Added
Attachment #43964|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85230
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85230
--- Comment #22 from Jakub Jelinek ---
Author: jakub
Date: Tue Apr 17 20:22:50 2018
New Revision: 259446
URL: https://gcc.gnu.org/viewcvs?rev=259446&root=gcc&view=rev
Log:
PR sanitizer/85230
* asan.c (handle_builtin_stack_restore
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84948
--- Comment #1 from Ian Lance Taylor ---
That is just the start of the problem. The garbage collector assumes that all
pointers are aligned to their natural boundary. That is, it expects that on a
system with four byte pointers, they are always
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84630
Paolo Carlini changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85430
--- Comment #4 from Zdenek Sojka ---
Observation about generated code:
$ x86_64-pc-linux-gnu-gcc -O2 -fno-tree-ccp -fno-tree-fre testcase.c -S -o-
...
foo:
movl%edi, %eax
addb%al, %al
ret
...
which looks superior
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85441
Jonathan Wakely changed:
What|Removed |Added
Keywords||compile-time-hog,
|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85424
--- Comment #1 from Michael Meissner ---
Author: meissner
Date: Tue Apr 17 18:22:08 2018
New Revision: 259441
URL: https://gcc.gnu.org/viewcvs?rev=259441&root=gcc&view=rev
Log:
2018-04-17 Michael Meissner
PR target/85424
* co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82686
--- Comment #15 from Dennis Clarke ---
The real issue here is libquadmath which seems to be based
on sources from Sun Microsystems software implementation of
the 128-bit floating point operations.
see 85440
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84842
Alexander Monakov changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85441
Bug ID: 85441
Summary: Empty loops not optimised away
Product: gcc
Version: 7.3.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85422
Tom de Vries changed:
What|Removed |Added
Known to fail||6.4.0, 7.3.0
--- Comment #2 from Tom de V
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85434
--- Comment #3 from Thomas Preud'homme ---
(In reply to Thomas Preud'homme from comment #2)
> (In reply to Thomas Preud'homme from comment #1)
> > This is caused by missing stack_protect_set and stack_protect_test pattern
> > in ARM backend. It w
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85440
Bug ID: 85440
Summary: libquadmath and quadmath.h do not exist on ppc64
Product: gcc
Version: 7.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85326
--- Comment #7 from ktkachov at gcc dot gnu.org ---
Author: ktkachov
Date: Tue Apr 17 17:06:36 2018
New Revision: 259437
URL: https://gcc.gnu.org/viewcvs?rev=259437&root=gcc&view=rev
Log:
PR testsuite/85326
Commit missing hunk from r259435.
Ad
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85430
--- Comment #3 from Jakub Jelinek ---
Author: jakub
Date: Tue Apr 17 17:01:31 2018
New Revision: 259436
URL: https://gcc.gnu.org/viewcvs?rev=259436&root=gcc&view=rev
Log:
PR target/85430
* config/i386/i386.md (*ashlqi3_1_slp): Us
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85326
--- Comment #6 from ktkachov at gcc dot gnu.org ---
Author: ktkachov
Date: Tue Apr 17 16:34:56 2018
New Revision: 259435
URL: https://gcc.gnu.org/viewcvs?rev=259435&root=gcc&view=rev
Log:
[AArch64/arm] PR testsuite/85326 Avoid C++ tests when C++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85439
Bug ID: 85439
Summary: mt19937_64 producing unexpected result only in certain
configuration
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85435
--- Comment #2 from Jonathan Wakely ---
The library will never call it with a null pointer, but users could do. Not
many people use char_traits directly though. Probably even fewer use the
primary template, because there are specializations for c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85436
--- Comment #1 from acsawdey at gcc dot gnu.org ---
Created attachment 43966
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43966&action=edit
shorter reduced test case
I've further reduced the test case and now it's only 38 lines so so shou
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85431
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85434
--- Comment #2 from Thomas Preud'homme ---
(In reply to Thomas Preud'homme from comment #1)
> This is caused by missing stack_protect_set and stack_protect_test pattern
> in ARM backend. It would be nice though if the address could be marked such
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85380
Ramana Radhakrishnan changed:
What|Removed |Added
CC||ebotcazou at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85203
Ramana Radhakrishnan changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82229
--- Comment #22 from krzysio.kurek at wp dot pl ---
I'm sorry but profiling doesn't seem to be well documented, what tools should I
use to generate a profiling log?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85435
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85437
Jakub Jelinek changed:
What|Removed |Added
CC||jason at gcc dot gnu.org
Target Milest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85437
--- Comment #4 from Jakub Jelinek ---
convert_ptrmem here creates a NOP_EXPR around the PTRMEM_CST, even when it is
for a static cast rather than reinterpret_cast. The OFFSET_TYPEs are
different, but they have the same TREE_TYPE etc.
Then conste
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85438
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55004
Bug 55004 depends on bug 85438, which changed state.
Bug 85438 Summary: [8 Regression] invalid "a reinterpret_cast is not a constant
expression" diagnostics since r249088
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85438
What|Rem
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85437
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85437
Marek Polacek changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85438
Jakub Jelinek changed:
What|Removed |Added
Keywords|accepts-invalid |rejects-valid
Status|UNCONFI
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85437
Martin Sebor changed:
What|Removed |Added
Keywords||rejects-valid
--- Comment #1 from Martin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70248
Martin Sebor changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85438
Bug ID: 85438
Summary: [8 Regression] invalid "a reinterpret_cast is not a
constant expression" diagnostics since r249088
Product: gcc
Version: 8.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85437
Bug ID: 85437
Summary: [8 Regression] member pointer static upcast rejected
in a constexpr context
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: norma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70248
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70248
--- Comment #4 from Martin Sebor ---
Rejecting the test case because of the initialization is a regression. The
cast is not a reinterpret cast. GCC gives the same error with a static cast
too:
$ gcc -S -Wall pr70248.C
pr70248.C:4:24: error: a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85436
Bug ID: 85436
Summary: [7 Regression] ICE compiling go code with -mcpu=power9
Product: gcc
Version: 7.3.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Compo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84637
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84442
--- Comment #4 from Jonathan Wakely ---
Dave, does the patch in comment 3 fix the FAIL?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85435
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85435
Bug ID: 85435
Summary: undefined behaviour in std::char_traits::move
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libst
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83077
Jonathan Wakely changed:
What|Removed |Added
Target Milestone|8.0 |9.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85434
Thomas Preud'homme changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85434
Bug ID: 85434
Summary: Address of stack protector guard spilled to stack on
ARM
Product: gcc
Version: 8.0.1
Status: UNCONFIRMED
Keywords: diagnostic
S
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71960
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85416
Alexander Monakov changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85433
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85416
--- Comment #13 from Alexander Monakov ---
This is most likely a variant of
https://bugzilla.redhat.com/show_bug.cgi?id=1421121
so hitting this bug requires a specific CPU model.
It looks as if SSE-AVX transition penalties appear when switc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85416
--- Comment #12 from Martin Reinecke ---
Created attachment 43961
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43961&action=edit
perf annotate output with -march=native
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85416
--- Comment #11 from Martin Reinecke ---
Created attachment 43960
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43960&action=edit
perf annotate output without -march=native
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85381
--- Comment #5 from Tom de Vries ---
(In reply to Tom de Vries from comment #4)
> This looks like a JIT bug, but with this tentative patch:
...
> no barriers are generated, and the minimized testcase passes.
And the original test-case passes.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85381
--- Comment #4 from Tom de Vries ---
This looks like a JIT bug, but with this tentative patch:
...
diff --git a/gcc/config/nvptx/nvptx.c b/gcc/config/nvptx/nvptx.c
index 8c478c874bd..ac394ee1ae6 100644
--- a/gcc/config/nvptx/nvptx.c
+++ b/gcc/con
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85416
--- Comment #10 from Martin Liška ---
And please rebuild the binaries with -g and attach perf annotate output.
Thanks.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85416
--- Comment #9 from Martin Reinecke ---
Sure!
martin@martin-Latitude-E7450 ~/tmp $ gcc -O3 testcase2.c -lm
martin@martin-Latitude-E7450 ~/tmp $ perf stat ./a.out
Performance counter stats for './a.out':
1109,985866 task-clock (mse
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85416
Alexander Monakov changed:
What|Removed |Added
CC||amonakov at gcc dot gnu.org
--- Comm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70248
--- Comment #3 from Jonathan Wakely ---
GCC trunk (8.0.1 20180410) now rejects comment 0 with:
c0.cc:4:24: error: a reinterpret_cast is not a constant expression
constexpr int A::*bx = (int(A::*))&B::x;
^
c0.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85433
Bug ID: 85433
Summary: -fdiagnostics-color=auto doesn't work properly with
LTO
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Prio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85428
Jonathan Wakely changed:
What|Removed |Added
Keywords||rejects-valid
Status|UNCON
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85432
Martin Liška changed:
What|Removed |Added
Version|unknown |8.0.1
Severity|normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85432
Bug ID: 85432
Summary: Wodr can be more verbose for C code
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: lto
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85417
--- Comment #5 from H.J. Lu ---
(In reply to Uroš Bizjak from comment #4)
> (In reply to H.J. Lu from comment #2)
> > I am working to enable CET on Linux with a single binary. -fcf-protection
> > should provide CET protection on x86 by default.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85391
Martin Liška changed:
What|Removed |Added
Assignee|marxin at gcc dot gnu.org |hubicka at gcc dot
gnu.org
--- Co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85381
--- Comment #3 from Tom de Vries ---
(In reply to Tom de Vries from comment #2)
> I minimized this failure, and ran into PR 80035/81069, so I've backported
> the fix from trunk: https://gcc.gnu.org/ml/gcc-patches/2018-04/msg00774.html
With that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84637
--- Comment #2 from Martin Liška ---
Thanks for explanation. Do you plan to remove it in the future from GCC or will
you leave it there unmaintained?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84640
Martin Liška changed:
What|Removed |Added
Status|WAITING |NEW
--- Comment #2 from Martin Liška ---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85431
Martin Liška changed:
What|Removed |Added
Version|unknown |8.0.1
Blocks|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85431
Bug ID: 85431
Summary: UBSAN: ../../gcc/dse.c:303:15: runtime error: shift
exponent 64 is too large for 64-bit type 'long
unsigned int'
Product: gcc
Version: unkn
1 - 100 of 119 matches
Mail list logo