public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/57059] [4.8/4.9/5 Regression] Host configuration of loose_warn breaks for build components for Canadian crosses
Date: Wed, 11 Mar 2015 17:19:00 -0000 [thread overview]
Message-ID: <bug-57059-4-1IdJxVG4NM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57059-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57059
Aldy Hernandez <aldyh at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |aldyh at gcc dot gnu.org
--- Comment #7 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
I can't reproduce this on mainline.
I'm building:
/source/gcc/configure --host=ppc64-linux --target=i386-elf
--build=x86-64-linux-gnu
I am cheating with the cross tools by setting links to native compilers to
speed up the process. My x86-64 build compilers are 4.6 based (gcc, g++,
x86-64-unknown-linux-gnu-gcc, etc in the list below) and do not have support
for -Wnarrowing. My cross compiler is ppc64-linux-g* which is the system
compiler and supports -Wnarrowing:
-rwxr-xr-x. 4 aldyh aldyh 1027379 Mar 11 08:16 c++
-rwxr-xr-x. 1 aldyh aldyh 1024943 Mar 11 08:16 cpp
-rwxr-xr-x. 4 aldyh aldyh 1027379 Mar 11 08:16 g++
-rwxr-xr-x. 3 aldyh aldyh 1022232 Mar 11 08:16 gcc
-rwxr-xr-x. 1 aldyh aldyh 135016 Mar 11 08:16 gcov
lrwxrwxrwx. 1 aldyh aldyh 11 Mar 11 09:36 ppc64-linux-ar -> /usr/bin/ar
lrwxrwxrwx. 1 aldyh aldyh 11 Mar 11 09:36 ppc64-linux-as -> /usr/bin/as
lrwxrwxrwx. 1 aldyh aldyh 12 Mar 11 09:51 ppc64-linux-g++ -> /usr/bin/g++
lrwxrwxrwx. 1 aldyh aldyh 12 Mar 11 09:51 ppc64-linux-gcc -> /usr/bin/gcc
lrwxrwxrwx. 1 aldyh aldyh 11 Mar 11 09:36 ppc64-linux-ld -> /usr/bin/ld
lrwxrwxrwx. 1 aldyh aldyh 11 Mar 11 09:36 ppc64-linux-nm -> /usr/bin/nm
lrwxrwxrwx. 1 aldyh aldyh 16 Mar 11 09:36 ppc64-linux-objcopy ->
/usr/bin/objcopy
lrwxrwxrwx. 1 aldyh aldyh 16 Mar 11 09:36 ppc64-linux-objdump ->
/usr/bin/objdump
lrwxrwxrwx. 1 aldyh aldyh 15 Mar 11 09:36 ppc64-linux-ranlib ->
/usr/bin/ranlib
lrwxrwxrwx. 1 aldyh aldyh 16 Mar 11 09:36 ppc64-linux-readelf ->
/usr/bin/readelf
lrwxrwxrwx. 1 aldyh aldyh 14 Mar 11 09:36 ppc64-linux-strip ->
/usr/bin/strip
-rwxr-xr-x. 4 aldyh aldyh 1027379 Mar 11 08:16 x86_64-unknown-linux-gnu-c++
-rwxr-xr-x. 4 aldyh aldyh 1027379 Mar 11 08:16 x86_64-unknown-linux-gnu-g++
-rwxr-xr-x. 3 aldyh aldyh 1022232 Mar 11 08:16 x86_64-unknown-linux-gnu-gcc
-rwxr-xr-x. 3 aldyh aldyh 1022232 Mar 11 08:16
x86_64-unknown-linux-gnu-gcc-4.6.4
# build compiler with no support for -Wnarrowing:
reynosa:/build/gcc46/install/bin$ gcc -c -Wnarrowing a.c
cc1: error: unrecognized command line option ‘-Wnarrowing’
# cross compiler with support for -Wnarrowing:
reynosa:/build/gcc46/install/bin$ ppc64-linux-gcc -c -Wnarrowing a.c
reynosa:/build/gcc46/install/bin$
I see the GCC configury correctly determining that -Wnarrowing is available for
the cross compiler:
[gcc/config.log]
configure:6367: checking whether ppc64-linux-gcc supports -Wnarrowing
configure:6384: ppc64-linux-gcc -c -Wnarrowing conftest.c >&5
configure:6384: $? = 0
configure:6393: result: yes
...
...
acx_cv_prog_cc_warning__Wnarrowing=yes
However, building build/genconstants.o with the x86-64-linux 4.6 compiler does
not use -Wno-narrowing, and is being compiled correctly:
g++ -c -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -DGENERATOR_FILE -I. -Ibuild
-I/s
ource/gcc/gcc -I/source/gcc/gcc/build -I/source/gcc/gcc/../include
-I/source/gc
c/gcc/../libcpp/include \
-o build/genconstants.o /source/gcc/gcc/genconstants.c
Further in the build process, the cross compiler is being used correctly, but
this time with -Wno-narrowing as expected:
ppc64-linux-g++ -c -DIN_GCC_FRONTEND -g -O2 -DIN_GCC
-DCROSS_DIRECTORY_STRUCTURE -fno-exceptions -fno-rtti
-fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings
-Wcast-qual -Wmissing-format-attribute -Woverloaded-virtual -pedantic
-Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -fno-common
-DHAVE_CONFIG_H -I. -Ic -I/source/gcc/gcc -I/source/gcc/gcc/c
-I/source/gcc/gcc/../include -I/source/gcc/gcc/../libcpp/include
-I/source/gcc/gcc/../libdecnumber -I/source/gcc/gcc/../libdecnumber/dpd
-I../libdecnumber -I/source/gcc/gcc/../libbacktrace -o c/c-parser.o -MT
c/c-parser.o -MMD -MP -MF c/.deps/c-parser.TPo /source/gcc/gcc/c/c-parser.c
This was last confirmed by Andrew Pinski on 4.8. I am inclined to remove this
as a regression on GCC 5.
>From gcc-bugs-return-480095-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Mar 11 17:22:03 2015
Return-Path: <gcc-bugs-return-480095-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6284 invoked by alias); 11 Mar 2015 17:22:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 6012 invoked by uid 48); 11 Mar 2015 17:21:59 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/62173] [5 Regression] 64bit Arch can't ivopt while 32bit Arch can
Date: Wed, 11 Mar 2015 17:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jiwang at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 5.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-62173-4-nZuTq8pjBZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-62173-4@http.gcc.gnu.org/bugzilla/>
References: <bug-62173-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-03/txt/msg01239.txt.bz2
Content-length: 216
https://gcc.gnu.org/bugzilla/show_bug.cgi?idb173
--- Comment #34 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Any progress on this? This is a P1 PR, but no comments have been added for
more than a month...
next prev parent reply other threads:[~2015-03-11 17:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 18:07 [Bug bootstrap/57059] New: " rmansfield at qnx dot com
2013-04-24 18:37 ` [Bug bootstrap/57059] [4.8/4.9 Regression] " pinskia at gcc dot gnu.org
2013-05-15 6:15 ` pinskia at gcc dot gnu.org
2013-05-31 11:00 ` jakub at gcc dot gnu.org
2013-10-16 9:50 ` jakub at gcc dot gnu.org
2013-11-22 10:46 ` rguenth at gcc dot gnu.org
2014-05-22 9:06 ` [Bug bootstrap/57059] [4.8/4.9/4.10 " rguenth at gcc dot gnu.org
2014-12-19 13:37 ` [Bug bootstrap/57059] [4.8/4.9/5 " jakub at gcc dot gnu.org
2015-03-11 17:19 ` aldyh at gcc dot gnu.org [this message]
2015-03-11 18:30 ` aldyh at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-57059-4-1IdJxVG4NM@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).