From: Simon Marchi <simon.marchi@polymtl.ca>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>, gdb@sourceware.org
Subject: Re: Array out of bounds
Date: Sun, 5 Sep 2021 21:48:22 -0400 [thread overview]
Message-ID: <6e5e153c-e540-63d5-4f5d-e1e700ee08d7@polymtl.ca> (raw)
In-Reply-To: <20210905180613.ykl6f3lvsio46jdg@lug-owl.de>
On 2021-09-05 2:06 p.m., Jan-Benedict Glaw wrote:
> Hi!
>
> On Sun, 2021-09-05 08:40:35 +0200, Jan-Benedict Glaw <jbglaw@lug-owl.de> wrote:
>> Hi!
>>
>> As I started with automated building/testing the GNU Toolchain again,
>> I found this when building GDB (make all-gdb) with a fairly recent GCC
>> on a Linux system (PC) when GDB is configured for
>> --target=aarch64-linux:
>
> Just to add: Seems to be independent of a target. Produces the same
> warning/error for all tested targets using a current GCC.
>
> Thanks,
> Jan-Benedict
>
I just built gcc at 66bba4dc263d ("Daily bump."), and I don't see it.
Simon
next prev parent reply other threads:[~2021-09-06 1:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-05 6:40 Jan-Benedict Glaw
2021-09-05 18:06 ` Jan-Benedict Glaw
2021-09-06 1:48 ` Simon Marchi [this message]
2021-09-06 6:03 ` Jan-Benedict Glaw
2021-09-07 14:27 ` Simon Marchi
2021-09-06 10:24 ` Tom de Vries
2021-09-06 14:49 ` Tom de Vries
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=6e5e153c-e540-63d5-4f5d-e1e700ee08d7@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb@sourceware.org \
--cc=jbglaw@lug-owl.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).