https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87013
martin changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44400
Eric Gallager changed:
What|Removed |Added
CC||jason at redhat dot com,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87105
--- Comment #2 from Andrew Pinski ---
One more point is in C++ (a < b ? b : a) is a lvalue which might also interfer
with converting it into min/max.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87105
--- Comment #1 from Andrew Pinski ---
So I think it is an interesting interaction in that GCC cannot change a < b ? a
: b into MIN_EXPR. There might be a reasoning behind this, dealing with NaNs,
INF, etc.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87104
--- Comment #5 from Andrew Pinski ---
(In reply to eggert from comment #3)
> (In reply to Andrew Pinski from comment #2)
> > This seems like a target issue ...
>
> Although the code generated is target-dependent, the performance problem is
> not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87104
--- Comment #4 from eggert at cs dot ucla.edu ---
Created attachment 44597
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44597&action=edit
output when compiling fg.c with "gcc -O2 -S" on x86
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87104
--- Comment #3 from eggert at cs dot ucla.edu ---
(In reply to Andrew Pinski from comment #2)
> This seems like a target issue ...
Although the code generated is target-dependent, the performance problem is not
limited to x86-64. x86 has the same
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86647
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87105
Bug ID: 87105
Summary: Autovectorization [X86, SSE2, AVX2, DoublePrecision]
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Compo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86704
--- Comment #5 from Thomas Koenig ---
Author: tkoenig
Date: Sat Aug 25 21:31:30 2018
New Revision: 263856
URL: https://gcc.gnu.org/viewcvs?rev=263856&root=gcc&view=rev
Log:
2018-08-25 Thomas Koenig
PR libfortran/86704
* m4/m
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87104
Andrew Pinski changed:
What|Removed |Added
Keywords||missed-optimization
Target|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87104
--- Comment #1 from eggert at cs dot ucla.edu ---
Created attachment 44596
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44596&action=edit
output when compiling fg.c with "gcc -O2 -S" on x86-64
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87104
Bug ID: 87104
Summary: missed &, == optimization makes Emacs ~0.4% slower on
x86-64
Product: gcc
Version: 8.1.1
Status: UNCONFIRMED
Severity: normal
P
--no-create
--no-recursion
Thread model: posix
gcc version 9.0.0 20180825 (experimental) (GCC)
$ gfortran -c tmp1.F90 -o tmp1.o
f951: internal compiler error: new_symbol(): Symbol name too long
0x7b9711 gfc_internal_error(char const*, ...)
../../gcc-trunk/gcc/fortran/error.c:1362
0x84a838
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87102
Bug ID: 87102
Summary: FAIL: gnat.dg/debug11_pkg.adb scan-assembler
local_imported_func
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87101
Bug ID: 87101
Summary: FAIL: gnat.dg/config_pragma1.adb execution test
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ada
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87100
Bug ID: 87100
Summary: FAIL: gnat.dg/config_pragma1.adb execution test
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ada
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87093
--- Comment #2 from Tony E Lewis ---
Thanks for the response. Yes - that makes sense to me.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86907
--- Comment #4 from janus at gcc dot gnu.org ---
(In reply to Jürgen Reuter from comment #3)
> Janus, this is actually incredibly valuable information. Yes, I was always
> since ages building gcc/gfortran/g++ from the svn, and at some point
> comp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87059
Jeffrey A. Law changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87059
--- Comment #22 from Jeffrey A. Law ---
Author: law
Date: Sat Aug 25 19:12:36 2018
New Revision: 263855
URL: https://gcc.gnu.org/viewcvs?rev=263855&root=gcc&view=rev
Log:
PR tree-optimization/87059
* builtins.c (expand_builtin_st
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81958
--- Comment #3 from Jeffrey A. Law ---
I'd suggest leaving as a single bug for the Wuninitialized issue. There may be
other approaches to fixing it that are worth exploring. If we split into
multiple bugs for the various hunks of work DOM would
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86907
--- Comment #3 from Jürgen Reuter ---
(In reply to janus from comment #2)
> I cannot reproduce this at r263854.
>
> I think the error you report requires GCC to be configured with
> --enable-checking (this is on by default for non-release builds
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86907
--- Comment #2 from janus at gcc dot gnu.org ---
I cannot reproduce this at r263854.
I think the error you report requires GCC to be configured with
--enable-checking (this is on by default for non-release builds, but off for
releases).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86545
janus at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86545
--- Comment #8 from janus at gcc dot gnu.org ---
Author: janus
Date: Sat Aug 25 15:41:34 2018
New Revision: 263854
URL: https://gcc.gnu.org/viewcvs?rev=263854&root=gcc&view=rev
Log:
fix PR 86545
2018-08-25 Janus Weil
PR fortran/86545
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86704
Thomas Koenig changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87045
Thomas Koenig changed:
What|Removed |Added
Keywords||wrong-code
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86872
H.J. Lu changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79342
H.J. Lu changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86662
--- Comment #5 from jozefl at gcc dot gnu.org ---
Author: jozefl
Date: Sat Aug 25 12:10:28 2018
New Revision: 263853
URL: https://gcc.gnu.org/viewcvs?rev=263853&root=gcc&view=rev
Log:
Backport from mainline
PR target/86662
* gcc/tree.c (
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86662
--- Comment #4 from jozefl at gcc dot gnu.org ---
Author: jozefl
Date: Sat Aug 25 11:52:15 2018
New Revision: 263852
URL: https://gcc.gnu.org/viewcvs?rev=263852&root=gcc&view=rev
Log:
Backport from mainline
PR target/86662
* gcc/tree.c
Hello!
This happens when using the MacPorts package manager. First build
went fine, then packages like cctools and ld64 were upgraded, so
libgcc/GCC 7.3.0 had to be upgraded too. The new build fails
constantly with
rm -f stage_current
make[3]: Leaving directory `/opt/local/var/ma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87089
--- Comment #2 from Dmitry G. Dyachenko ---
gcc invocation can be simplified : -fno-semantic-interposition can be removed.
(was needed while creducing original testcase)
So,
$ g++ -fpreprocessed -O2 -flto -fPIC -DPIC -c -o a.o a.ii
$ g++ -fprepr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70694
--- Comment #8 from Iain Sandoe ---
Author: iains
Date: Sat Aug 25 09:02:28 2018
New Revision: 263850
URL: https://gcc.gnu.org/viewcvs?rev=263850&root=gcc&view=rev
Log:
Don't force visibility to hidden for Darwin > 8.
PR libstdc++/70694
35 matches
Mail list logo
