[Bug target/112465] libgcc: aarch64: lse runtime does not work with big data segments

2025-03-01 Thread mailboxnotfound at yahoo dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112465 john henning changed: What|Removed |Added CC||mailboxnotfound at yahoo dot com

[Bug bootstrap/101843] Build of binutils-2.37 with gcc-11.2.0 fails due to change to libiberty/hashtab.c

2021-08-11 Thread mailboxnotfound at yahoo dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101843 --- Comment #6 from john henning --- Let's simplify. Per Richard's comment #1, there won't be a code fix. OK. As to a doc fix, Richard wrote: "For release versions your milage may vary and we fail to document working version pairs" YES

[Bug bootstrap/101843] Build of binutils-2.37 with gcc-11.2.0 fails due to change to libiberty/hashtab.c

2021-08-10 Thread mailboxnotfound at yahoo dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101843 --- Comment #5 from john henning --- Andrew suggests: Combined source builds are not for released sources Respectfully, I suggest that the documentation disagrees. Please see the binutils paragraph of the documentation of the released version

[Bug bootstrap/101843] Build of binutils-2.37 with gcc-11.2.0 fails due to change to libiberty/hashtab.c

2021-08-10 Thread mailboxnotfound at yahoo dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101843 --- Comment #2 from john henning --- If this is a doc bug, then two documentation comments and one other thought. (1) https://gcc.gnu.org/gcc-11/changes.html says that certain functionality requires “Binutils version 2.36 or later”.

[Bug other/101843] New: Build of binutils-2.37 with gcc-11.2.0 fails due to change to libiberty/hashtab.c

2021-08-10 Thread mailboxnotfound at yahoo dot com via Gcc-bugs
Severity: normal Priority: P3 Component: other Assignee: unassigned at gcc dot gnu.org Reporter: mailboxnotfound at yahoo dot com Target Milestone: --- SUMMARY Building binutils along with GCC is a documented method, but it fails for gcc-11.2.0 with

[Bug target/84201] 549.fotonik3d_r from SPEC2017 fails verification with recent Intel and AMD CPUs

2020-09-17 Thread mailboxnotfound at yahoo dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84201 john henning changed: What|Removed |Added CC||mailboxnotfound at yahoo dot com

[Bug middle-end/82004] [8 Regression] SPEC CPU2017 628.pop2_s miscompare

2020-08-11 Thread mailboxnotfound at yahoo dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82004 --- Comment #47 from john henning --- SPEC next step: Because the performance differences were small (in my limited testing) no matter which workaround I picked (-O3, or remove Feedback Directed Optimization, or add -fno-unsafe-math-optimizations

[Bug middle-end/82004] [8 Regression] SPEC CPU2017 628.pop2_s miscompare

2020-08-07 Thread mailboxnotfound at yahoo dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82004 --- Comment #46 from john henning --- Created attachment 49027 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49027&action=edit More testing 7-aug-2020

[Bug middle-end/82004] [8 Regression] SPEC CPU2017 628.pop2_s miscompare

2020-08-07 Thread mailboxnotfound at yahoo dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82004 --- Comment #45 from john henning --- I had promised to do some more testing. There were miscompares during the training run (thus causing the build to fail) using -Ofast -flto -fprofile-generate/-fprofile-use on aarch64 with GCC 8.2,

[Bug middle-end/82004] [8 Regression] SPEC CPU2017 628.pop2_s miscompare

2020-08-06 Thread mailboxnotfound at yahoo dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82004 john henning changed: What|Removed |Added CC||mailboxnotfound at yahoo dot com

[Bug fortran/90656] New: Illegal operand from Fortran program WRF with mcpu=niagara3

2019-05-28 Thread mailboxnotfound at yahoo dot com
Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: mailboxnotfound at yahoo dot com Target Milestone: --- Created attachment 46426 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46426&action=edit tarball, md

[Bug target/88535] sparcv9 gcc 7 causes comparison failure in sparc gcc 8 dwarf2out.o

2018-12-18 Thread mailboxnotfound at yahoo dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88535 --- Comment #12 from john henning --- Summary: Eric's advice worked as prescribed. Detail: On a SPARC Solaris 11.4 system, with a /usr/bin/gcc that by default produces 64-bit objects, this worked for an 8.2.0 bootstrap build: export CC=

[Bug target/88535] sparcv9 gcc 7 causes comparison failure in sparc gcc 8 dwarf2out.o

2018-12-18 Thread mailboxnotfound at yahoo dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88535 --- Comment #11 from john henning --- > There are 3 different switches: --build, --host and --target. Hmm. I must be looking in the wrong place for documentation; are these explained somewhere? At https://gcc.gnu.org/install/configure.html I

[Bug target/88535] sparcv9 gcc 7 causes comparison failure in sparc gcc 8 dwarf2out.o

2018-12-18 Thread mailboxnotfound at yahoo dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88535 --- Comment #9 from john henning --- Eric, thank you for the explicit advice, although I note that both your examples say '--build=something'. Is that switch similar to or different from the switch '--target=something', which http://gcc.gnu.or

[Bug target/88535] sparcv9 gcc 7 causes comparison failure in sparc gcc 8 dwarf2out.o

2018-12-18 Thread mailboxnotfound at yahoo dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88535 --- Comment #5 from john henning --- Thank you for the response. I wonder if the configure or make process should defend against the possibility that the host compiler and the compiler that we are building today have differing defaults for -m3

[Bug target/88535] sparcv9 gcc 7 causes comparison failure in sparc gcc 8 dwarf2out.o

2018-12-18 Thread mailboxnotfound at yahoo dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88535 --- Comment #3 from john henning --- Rainer points out that a key here seems to be that the host system compiler had been configured with sparcv9-solaris2.11 but the 8.2.0 build did not request the same. In my case, the host system compiler was

[Bug target/88535] sparcv9 gcc 7 causes comparison failure in sparc gcc 8 dwarf2out.o

2018-12-18 Thread mailboxnotfound at yahoo dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88535 john henning changed: What|Removed |Added CC||mailboxnotfound at yahoo dot com

[Bug lto/83201] [7/8 Regression] SPEC CPU2017 505.mcf_r produces incorrect output when built with -flto and FDO

2018-05-09 Thread mailboxnotfound at yahoo dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83201 john henning changed: What|Removed |Added CC||mailboxnotfound at yahoo dot com