public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tobias Burnus <tobias@codesourcery.com>
To: Jakub Jelinek <jakub@redhat.com>,
	Richard Biener <rguenther@suse.de>,
	Jason Merrill <jason@redhat.com>,
	"Joseph S. Myers" <joseph@codesourcery.com>
Cc: <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] driver, cppdefault: Unbreak bootstrap on Debian/Ubuntu [PR107059]
Date: Thu, 29 Sep 2022 11:23:00 +0200	[thread overview]
Message-ID: <a9fe6108-f999-988a-d9ba-05aeb9d6a276@codesourcery.com> (raw)
In-Reply-To: <YzVECKV7e5nDSA0S@tucnak>

[-- Attachment #1: Type: text/plain, Size: 3123 bytes --]

On 29.09.22 09:06, Jakub Jelinek wrote:

My recent change to enable _Float{16,32,64,128,32x,64x,128x} for C++
apparently broke bootstrap on some Debian/Ubuntu setups.
Those multiarch targets put some headers into
/usr/include/x86_64-linux-gnu/bits/ etc. subdirectory instead of
/usr/include/bits/.

...

Bootstrapped/regtested on x86_64-linux (Debian on GCCFarm, though with the
/usr/include/bits -> x86_64-linux-gnu/bits symlink).  Ok for trunk?


I have now bootstrapped on ppc64le with Ubuntu 18.04.3 LTS (bionic) with glibc 2.27-3ubuntu1

This glibc is too old for the '#   if __LDBL_MANT_DIG__ == 113"' issue reported by
Joseph as that line was added one version later in glibc 2.28.

But it did have the bootstrap issue (only affecting the -B... / build, the installed
one was okay - for reasons why, see PR).

Thus, my boostrap only tested this patch - and not the __LDBL_MANT_DIG__ part.

Result: Bootstrapping passed and I get for

cd $BUILD
echo '#include <complex.h>' > foo.c
gcc/xgcc -B`pwd`/gcc -v -E -o foo.i foo.c
grep floatn.h foo.i

...
/tmp/gcc-build/gcc/cc1 ... \
  -iprefix /tmp/tburnus-gcc-test/gcc/../lib/gcc/powerpc64le-unknown-linux-gnu/13.0.0/ \
  -isystem /tmp/tburnus-gcc-test/gcc/include \
  -isystem /tmp/tburnus-gcc-test/gcc/include-fixed/powerpc64le-linux-gnu \
  -isystem /tmp/tburnus-gcc-test/gcc/include-fixed
...
#include "..." search starts here:
#include <...> search starts here:
 /tmp/gcc-build/gcc/include
 /tmp/gcc-build/gcc/include-fixed/powerpc64le-linux-gnu
 /tmp/gcc-build/gcc/include-fixed
 /usr/local/include
 /usr/include/powerpc64le-linux-gnu
 /usr/include
End of search list.
...
# 1 "/tmp/gcc-build/gcc/include-fixed/powerpc64le-linux-gnu/bits/floatn.h" 1 3 4

 * * *

And with the installed version:

#include "..." search starts here:
#include <...> search starts here:
 /tmp/gcc-inst/lib/gcc/powerpc64le-unknown-linux-gnu/13.0.0/include
 /usr/local/include
 /tmp/gcc-inst/include
 /tmp/gcc-inst/lib/gcc/powerpc64le-unknown-linux-gnu/13.0.0/include-fixed/powerpc64le-linux-gnu
 /tmp/gcc-inst/lib/gcc/powerpc64le-unknown-linux-gnu/13.0.0/include-fixed
 /usr/include/powerpc64le-linux-gnu
 /usr/include
End of search list.
...
# 1 "/tmp/gcc-inst/lib/gcc/powerpc64le-unknown-linux-gnu/13.0.0/include-fixed/powerpc64le-linux-gnu/bits/floatn.h" 1 3 4
...

Thanks for the fix!

Tobias


2022-09-29  Jakub Jelinek  <jakub@redhat.com><mailto:jakub@redhat.com>

        PR bootstrap/107059
        * cppdefault.cc (cpp_include_defaults): If SYSROOT_HEADERS_SUFFIX_SPEC
        isn't defined, add FIXED_INCLUDE_DIR entry with multilib flag 2
        before FIXED_INCLUDE_DIR entry with multilib flag 0.
        * gcc.cc (do_spec_1): If multiarch_dir, add
        include-fixed/multiarch_dir paths before include-fixed paths.


-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955

      parent reply	other threads:[~2022-09-29  9:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-29  7:06 Jakub Jelinek
2022-09-29  8:26 ` Richard Biener
2022-09-29  9:23 ` Tobias Burnus [this message]

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=a9fe6108-f999-988a-d9ba-05aeb9d6a276@codesourcery.com \
    --to=tobias@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=jason@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=rguenther@suse.de \
    /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).