From: Marc Glisse <marc.glisse@inria.fr>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: Jonathan Wakely <jwakely@redhat.com>,
Iain Sandoe <iain@sandoe.co.uk>,
libstdc++ <libstdc++@gcc.gnu.org>,
GCC Patches <gcc-patches@gcc.gnu.org>,
"CHIGOT, CLEMENT" <clement.chigot@atos.net>
Subject: Re: [PATCH, libstdc++] GLIBCXX_HAVE_INT64_T
Date: Wed, 6 Jan 2021 19:55:28 +0100 (CET) [thread overview]
Message-ID: <82157de3-8afb-48a-44be-a8b38a7d7e44@stedding.saclay.inria.fr> (raw)
In-Reply-To: <CAGWvnyk0q7RSgiwKr-e5R002JRrq+udBCNdaukWHRD-3L=DWgA@mail.gmail.com>
On Wed, 6 Jan 2021, David Edelsohn via Gcc-patches wrote:
> Currently the type of streamoff is determined at libstdc++ configure
> time, chosen by the definitions of _GLIBCXX_HAVE_INT64_T_LONG and
> _GLIBCXX_HAVE_INT64_T_LONG_LONG. For a multilib configuration, the
> difference is encoded in the different multilib header file paths.
> For "FAT" library targets that package 32 bit and 64 bit libraries
> together, G++ also expects a single header file directory hierarchy,
> causing an incorrect value for streamoff in some situations.
Shouldn't we change that? I don't see why using the same directory for
linking should imply using the same directory for includes.
--
Marc Glisse
next prev parent reply other threads:[~2021-01-06 18:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 18:38 David Edelsohn
2021-01-06 18:55 ` Marc Glisse [this message]
2021-01-06 19:11 ` David Edelsohn
2021-01-06 19:37 ` Jakub Jelinek
2021-01-06 21:20 ` David Edelsohn
2021-01-06 21:41 ` Jakub Jelinek
2021-01-06 23:01 ` David Edelsohn
2021-01-06 23:39 ` Jakub Jelinek
2021-01-06 23:45 ` Jakub Jelinek
2021-01-07 0:41 ` David Edelsohn
2021-01-08 18:37 ` Jonathan Wakely
2021-01-08 18:52 ` Jakub Jelinek
2021-01-08 20:35 ` David Edelsohn
2021-04-29 20:06 ` David Edelsohn
2021-04-29 20:23 ` Jonathan Wakely
2021-04-30 19:31 ` Jonathan Wakely
2021-04-30 20:18 ` David Edelsohn
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=82157de3-8afb-48a-44be-a8b38a7d7e44@stedding.saclay.inria.fr \
--to=marc.glisse@inria.fr \
--cc=clement.chigot@atos.net \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iain@sandoe.co.uk \
--cc=jwakely@redhat.com \
--cc=libstdc++@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).