From: Xi Ruoyao <xry111@xry111.site>
To: Detlef Vollmann <dv@vollmann.ch>,
gcc Patches <gcc-patches@gcc.gnu.org>,
libstdc++ <libstdc++@gcc.gnu.org>
Cc: gcc-bugzilla@gcc.gnu.org
Subject: Re: [PATCH] libstdc++: Fix build for AVR [PR115481, PR111639]
Date: Sat, 15 Jun 2024 01:45:09 +0800 [thread overview]
Message-ID: <0f5c75f9e6a51cd1ad9eb1274bf93d9b310af2b2.camel@xry111.site> (raw)
In-Reply-To: <05fec570-04e5-44de-9a61-c25fb1adf92d@vollmann.ch>
On Fri, 2024-06-14 at 19:37 +0200, Detlef Vollmann wrote:
> diff --git a/libstdc++-v3/configure b/libstdc++-v3/configure
> index 5645e991af7..17dbae7bd87 100755
> --- a/libstdc++-v3/configure
> +++ b/libstdc++-v3/configure
> @@ -5080,7 +5080,7 @@ else
> We can't simply define LARGE_OFF_T to be 9223372036854775807,
> since some C++ compilers masquerading as C compilers
> incorrectly reject 9223372036854775807. */
> -#define LARGE_OFF_T (((off_t) 1 << 62) - 1 + ((off_t) 1 << 62))
> +#define LARGE_OFF_T ((((off_t) 1 << 31) << 31) - 1 + (((off_t) 1 << 31) << 31))
> int off_t_is_large[(LARGE_OFF_T % 2147483629 == 721
> && LARGE_OFF_T % 2147483647 == 1)
> ? 1 : -1];
This shouldn't happen. Please regenerate using *vanilla* autoconf-2.69.
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2024-06-14 17:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-115481-3249@http.gcc.gnu.org/bugzilla/>
[not found] ` <bug-115481-3249-15VyLpgmpe@http.gcc.gnu.org/bugzilla/>
2024-06-14 17:37 ` Detlef Vollmann
2024-06-14 17:45 ` Xi Ruoyao [this message]
2024-06-14 17:59 ` Jonathan Wakely
2024-06-18 12:56 ` [PATCH v2] " Detlef Vollmann
2024-06-14 19:11 ` [PATCH] " Detlef Vollmann
2024-06-15 8:30 ` Georg-Johann Lay
2024-06-15 20:28 ` Detlef Vollmann
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=0f5c75f9e6a51cd1ad9eb1274bf93d9b310af2b2.camel@xry111.site \
--to=xry111@xry111.site \
--cc=dv@vollmann.ch \
--cc=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--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).