https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88343
Segher Boessenkool changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88343
--- Comment #13 from Iain Sandoe ---
(In reply to Joseph S. Myers from comment #11)
> This change results in miscompilation of glibc for 32-bit soft-float powerpc
> (symptoms: many libm tests as run by "make regen-ulps" either segfault, or
> prod
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88669
Bug ID: 88669
Summary: Contiguous attribute wrongly rejected
Product: gcc
Version: 8.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88599
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88343
--- Comment #14 from Iain Sandoe ---
Author: iains
Date: Thu Jan 3 08:34:41 2019
New Revision: 267542
URL: https://gcc.gnu.org/viewcvs?rev=267542&root=gcc&view=rev
Log:
revert fix for pr88343
causes problems with soft-fp in GLIBC, see pr comme
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88147
--- Comment #8 from Martin Liška ---
(In reply to David Malcolm from comment #7)
> I've been trying to reproduce this, but failing - I tried with today's
> trunk, and with a build from 2018-11-16.
>
> Do you have a revision that is known to trig
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80362
--- Comment #10 from Richard Biener ---
(In reply to Alexandre Oliva from comment #9)
> I see the same issue of using arg vs op is present in the reciprocal tests
> right below the patched ones. AFAICT it is not possible to trigger the
> problem
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88666
Richard Biener changed:
What|Removed |Added
Keywords||needs-bisection
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88343
--- Comment #15 from Iain Sandoe ---
Author: iains
Date: Thu Jan 3 08:45:35 2019
New Revision: 267543
URL: https://gcc.gnu.org/viewcvs?rev=267543&root=gcc&view=rev
Log:
revert fix for pr88343
This causes problems for soft-f on GLIBC, see pr co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88568
Richard Biener changed:
What|Removed |Added
Keywords||wrong-code
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88570
Richard Biener changed:
What|Removed |Added
Blocks||53947
--- Comment #4 from Richard Biene
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88561
--- Comment #6 from Martin Liška ---
Author: marxin
Date: Thu Jan 3 08:49:04 2019
New Revision: 267546
URL: https://gcc.gnu.org/viewcvs?rev=267546&root=gcc&view=rev
Log:
Backport r267507
2019-01-03 Martin Liska
Backport from mainli
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88273
Martin Liška changed:
What|Removed |Added
Target||powerpc-*-linux-gnu
Status|UN
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88644
--- Comment #5 from Iain Sandoe ---
(In reply to Iain Sandoe from comment #4)
> will do a complete test suite run now, to catch any other changed lengths.
I don't see any other related changes.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88666
--- Comment #3 from Martin Liška ---
(In reply to Richard Biener from comment #2)
> Confirmed with GCC 8.2.0, I can't reproduce it on the branch head so I
> assume it was fixed (and there was likely a duplicate report). Martin, can
> you bisect
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87099
Martin Liška changed:
What|Removed |Added
CC||geir at cray dot com
--- Comment #7 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88666
Martin Liška changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88331
Rainer Emrich changed:
What|Removed |Added
CC||rai...@emrich-ebersheim.de
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88592
Eric Botcazou changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88563
Martin Liška changed:
What|Removed |Added
CC||marxin at gcc dot gnu.org
--- Comment #7
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88592
Eric Botcazou changed:
What|Removed |Added
Status|NEW |SUSPENDED
--- Comment #2 from Eric Botca
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87554
--- Comment #6 from Martin Liška ---
With first bad revision the constructor looks as follows:
$ (gdb) p print_generic_expr(stderr, decl->decl_common.initial, 0)
instance = b::create ()$1 = void
(gdb) p debug_tree(decl->decl_common.initial)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88331
--- Comment #7 from Rainer Emrich ---
If I call make within the libgfortran directory I get a slightly different
error message:
during RTL pass: postreload
../../../../../../../../opt/devel/gnu/src/gcc-mingw-w64/gcc-9.0.0/libgfortran/generated/m
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88610
Eric Botcazou changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88331
--- Comment #8 from Rainer Emrich ---
Created attachment 45323
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45323&action=edit
preprocessed source
I attached the preprocessed source.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88636
--- Comment #1 from Jakub Jelinek ---
Author: jakub
Date: Thu Jan 3 10:11:40 2019
New Revision: 267548
URL: https://gcc.gnu.org/viewcvs?rev=267548&root=gcc&view=rev
Log:
PR c++/88636
* decl.c (builtin_function_1): Return result
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83651
--- Comment #18 from Martin Liška ---
This is what I see on my model name : Intel(R) Core(TM) i7-4770 CPU @
3.40GHz:
gcc-bisect.py bisect 'gcc -O2 aes_generic.c && /usr/bin/time -f '%E' ./a.out'
-o
Releases
4.8.0 (e9c762ec4671d77e)(22 Mar
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88636
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88273
Martin Liška changed:
What|Removed |Added
Keywords|needs-bisection |
Known to fail|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87880
--- Comment #9 from Iain Sandoe ---
So.. this is somewhat puzzling.
Essentially, it seems that on macOS and Linux (at least) currently
ASAN_INTERCEPT___CXA_RETHROW_PRIMARY_EXCEPTION is set unconditionally to "on"
(for any target that has ASAN_HA
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48543
Tamar Christina changed:
What|Removed |Added
CC||tnfchris at gcc dot gnu.org
--- Commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88644
--- Comment #6 from Jakub Jelinek ---
Author: jakub
Date: Thu Jan 3 11:05:24 2019
New Revision: 267550
URL: https://gcc.gnu.org/viewcvs?rev=267550&root=gcc&view=rev
Log:
PR debug/88644
* dwarf2out.c (modified_type_die): If type
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88669
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88535
--- Comment #16 from Rainer Orth ---
Author: ro
Date: Thu Jan 3 11:28:27 2019
New Revision: 267551
URL: https://gcc.gnu.org/viewcvs?rev=267551&root=gcc&view=rev
Log:
Update config.guess, config.sub (PR target/88535)
PR target/88535
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48543
Dominique d'Humieres changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83651
--- Comment #19 from Richard Biener ---
Not sure what you are talking about - your numbers confirm the regression is
still present? Or do you mean that GCC 7.1.0 is also bad and only 6.x was OK
(which didn't have code hoisting?)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88670
Bug ID: 88670
Summary: [meta-bug] generic vector extension issues
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-e
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88670
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83651
--- Comment #20 from Martin Liška ---
(In reply to Richard Biener from comment #19)
> Not sure what you are talking about - your numbers confirm the regression is
> still present? Or do you mean that GCC 7.1.0 is also bad and only 6.x was OK
> (
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54939
Richard Biener changed:
What|Removed |Added
CC||segher at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88063
Tom de Vries changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85574
--- Comment #26 from Richard Biener ---
Author: rguenth
Date: Thu Jan 3 12:23:27 2019
New Revision: 267552
URL: https://gcc.gnu.org/viewcvs?rev=267552&root=gcc&view=rev
Log:
2019-01-03 Jan Hubicka
PR tree-optimization/85574
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48543
--- Comment #7 from Thomas Koenig ---
Author: tkoenig
Date: Thu Jan 3 12:32:34 2019
New Revision: 267553
URL: https://gcc.gnu.org/viewcvs?rev=267553&root=gcc&view=rev
Log:
2019-01-02 Thomas Koenig
PR fortran/48543
* gfortran.dg/cons
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54939
--- Comment #9 from Segher Boessenkool ---
I think we should declare one of the forms canonical, and make simplify
use that one, if possible. If we really want one form in some cases and
another in other cases something like change_zero_ext will
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88668
--- Comment #4 from Umesh Kalappa ---
Thank you Andrew for the suggestions and let us try the same and update here .
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54939
--- Comment #10 from rguenther at suse dot de ---
On Thu, 3 Jan 2019, segher at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54939
>
> --- Comment #9 from Segher Boessenkool ---
> I think we should declare one of the f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54939
--- Comment #11 from Segher Boessenkool ---
(In reply to rguent...@suse.de from comment #10)
> even if that means introducing of "fake" larger vector modes.
That would be a good reason to not do this, except many targets already
do need double-l
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88669
Thomas Koenig changed:
What|Removed |Added
CC||tkoenig at gcc dot gnu.org
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54939
--- Comment #12 from Uroš Bizjak ---
(In reply to Richard Biener from comment #8)
> Maybe combine itself can try both variants in case there's a duality
> between (vec_merge ...) and (vec_select (vec_concat ...))?
Please note that combine spli
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88671
Bug ID: 88671
Summary: generic vector passed in MMX regs
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88671
Richard Biener changed:
What|Removed |Added
Keywords||ABI
Target|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88672
Bug ID: 88672
Summary: friend class template declaration in a class template
is ignored
Product: gcc
Version: 8.2.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54939
--- Comment #13 from rguenther at suse dot de ---
On Thu, 3 Jan 2019, segher at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54939
>
> --- Comment #11 from Segher Boessenkool ---
> (In reply to rguent...@suse.de from c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88619
--- Comment #3 from Jakub Jelinek ---
Created attachment 45324
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45324&action=edit
gcc9-pr88619.patch
Untested fix. make check-gcc check-c++-all
RUNTESTFLAGS='--target_board=unix\{-m32,-m64\} a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88671
--- Comment #2 from Uroš Bizjak ---
This is required by ABI, please see section 2.3.3 of i386 PSABI, where:
The exceptions to parameters passed on stack are as follows:
• The first three parameters of type __m64 are passed in %mm0, %mm1, and %mm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88673
Bug ID: 88673
Summary: Overflowed array index read error
Product: gcc
Version: 6.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88671
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88674
Bug ID: 88674
Summary: GCC thinks that register is a qualifier in function
declaration with no parameters.
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88675
Bug ID: 88675
Summary: std::make_integer_sequence not working for enums
Product: gcc
Version: 8.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88654
--- Comment #3 from Iain Buclaw ---
(In reply to Jakub Jelinek from comment #0)
> The reason I'm filing this is that there are multiple issues:
>
> 1) what I'm worried about most is that the timeouts for tests don't work, it
> happens that some
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88598
rsandifo at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assigne
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88671
H.J. Lu changed:
What|Removed |Added
CC||hjl.tools at gmail dot com
--- Comment #4 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88676
Bug ID: 88676
Summary: missed opportunity is integer conditional
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-opti
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88654
--- Comment #4 from Jakub Jelinek ---
(In reply to Iain Buclaw from comment #3)
> (In reply to Jakub Jelinek from comment #0)
> > The reason I'm filing this is that there are multiple issues:
> >
> > 1) what I'm worried about most is that the ti
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84478
--- Comment #10 from H.J. Lu ---
(In reply to Rainer Orth from comment #5)
> The new testcase FAILs e.g. on i386-pc-solaris2.11 and sparc-sun-solaris2.11
> (32-bit only) at -O1 and above:
>
> +FAIL: gcc.c-torture/execute/pr84478.c -O1 executi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88598
--- Comment #6 from rsandifo at gcc dot gnu.org
---
I think a general fix for this would involve tracking the set of
nonzero vector elements and adding a match.pd rule that uses that
to replace REDUC functions in which only one element of the
ar
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88669
--- Comment #3 from Thomas Koenig ---
Works when class(t) is replaced by type(t), so the attributes
were not correctly set somewhere.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88598
--- Comment #7 from rguenther at suse dot de ---
On Thu, 3 Jan 2019, rsandifo at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88598
>
> --- Comment #6 from rsandifo at gcc dot gnu.org
> ---
> I think a general fix for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88677
Bug ID: 88677
Summary: Divergence in -O2 and -O2 -flto early opts
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: lto
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88677
--- Comment #1 from Jan Hubicka ---
Created attachment 45326
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45326&action=edit
dump with no lto
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88677
--- Comment #2 from Jan Hubicka ---
Created attachment 45327
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45327&action=edit
dump with lto
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86891
--- Comment #4 from Richard Earnshaw ---
Yes, the extension should be zero-extend, not sign extend. The plus operation
is correct, however, since decrementing the first operand could lead to
underflow if it was zero. So the correct rtl would be
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88678
Bug ID: 88678
Summary: [9 regression] Many gfortran.dg/ieee/ieee_X.f90 test
cases fail starting with r267465
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Sever
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88677
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88678
--- Comment #1 from kargl at gcc dot gnu.org ---
(In reply to seurer from comment #0)
> Program received signal SIGFPE: Floating-point exception - erroneous
> arithmetic operation.
>
> Backtrace for this error:
> #0 0x3fffb00304d7 in ???
What
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88677
--- Comment #4 from Jan Hubicka ---
This drops TYPE_NEEDS_CONSTRUCTING. I checked the uses
jan@skylake:~/trunk/gcc> grep TYPE_NEEDS_CONSTRU *.c
gimplify.c: || TYPE_NEEDS_CONSTRUCTING (TREE_TYPE (decl
print-tree.c: if (TYPE_NEEDS_C
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88677
Martin Liška changed:
What|Removed |Added
Keywords||needs-reduction
--- Comment #5 from Marti
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88027
acsawdey at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88675
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88679
Bug ID: 88679
Summary: SSE2 intrinsics are available by default on x86
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88343
--- Comment #16 from joseph at codesourcery dot com ---
On Thu, 3 Jan 2019, iains at gcc dot gnu.org wrote:
> Unfortunately, there doesn't appear to be anything in the GCC test suite that
> catches this (all languages reg-strap was clean, on gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88679
H.J. Lu changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88673
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88510
--- Comment #2 from Devin Hussey ---
Update: I did the calculations, and twomul has the same cycle count as
goodmul_sse. vmul.i32 with 128-bit operands takes 4 cycles (I assumed it was
two), so just like goodmul_sse, it takes 11 cycles.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88672
--- Comment #1 from Jonathan Wakely ---
Please check if this is a duplicate of one of the bugs that PR 59002 depends
on.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88672
--- Comment #2 from Jonathan Wakely ---
Also, https://gcc.gnu.org/bugs very clearly says we need the testcase in
bugzilla, and not just a URL to some other site.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88674
--- Comment #1 from joseph at codesourcery dot com ---
"qualified" is used in the informal sense of "any additional specifiers
along with void", not in the sense of "type qualifiers present". The
program is not valid. J.2 explicitly lists "A
with: ../gcc-trunk-20190103/configure
--prefix=/opt/compiler-explorer/gcc-build/staging --build=x86_64-linux-gnu
--host=x86_64-linux-gnu --target=x86_64-linux-gnu --disable-bootstrap
--enable-multiarch --with-abi=m64 --with-multilib-list=m32,m64,mx32
--enable-multilib --enable-clocale=gnu --enable
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88680
Bug ID: 88680
Summary: [9 Regression] bogus -Wtype-limits for constant
expressions after r267272
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88679
--- Comment #3 from H.J. Lu ---
Your GCC is configured -m32 ISA to x86-64 ISA by default. To default -m32 ISA
to i686 ISA, please configure your GCC with --with-arch_32=i686. Or you can
use
"-march=i686 -m32".
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88343
--- Comment #17 from Joseph S. Myers ---
Created attachment 45328
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45328&action=edit
Preprocessed source
Replacing s_nextafterf.os built with trunk with that patch reverted, by the
same file as
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88343
--- Comment #18 from Joseph S. Myers ---
Created attachment 45329
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45329&action=edit
Good assembly (with the GCC patch reverted)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88343
--- Comment #19 from Joseph S. Myers ---
Created attachment 45330
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45330&action=edit
Bad assembly (from trunk r267560 with the patch still present)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88679
H.J. Lu changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88620
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88681
Bug ID: 88681
Summary: Missing symbol exports in libstdc++.so
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc+
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88681
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88681
--- Comment #1 from Jonathan Wakely ---
N.B. When optimization is enabled the functions are inlined, so the exports
aren't needed.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88678
--- Comment #2 from seurer at gcc dot gnu.org ---
Program received signal SIGFPE: Floating-point exception - erroneous arithmetic
operation.
Backtrace for this error:
#0 0x3fffb17f0477 in ???
#1 0x3fffb14f1694 in feenableexcept
at ../sy
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88616
Jakub Jelinek changed:
What|Removed |Added
CC||aoliva at gcc dot gnu.org,
1 - 100 of 159 matches
Mail list logo