public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "clyon at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/95757] [11 regression] missing warning in gcc.dg/Wstringop-overflow-25.c since r11-1517
Date: Fri, 19 Jun 2020 07:35:08 +0000 [thread overview]
Message-ID: <bug-95757-4-OqyilU2za4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95757-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95757
Christophe Lyon <clyon at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target|powerpc64*-linux-gnu |powerpc64*-linux-gnu arm
CC| |clyon at gcc dot gnu.org
--- Comment #1 from Christophe Lyon <clyon at gcc dot gnu.org> ---
I see the same thing on some arm targets:
arm-none-linux-gnueabihf --with-cpu=cortex-a5
arm-none-eabi -mcpu=cortex-m[034]
but for instance arm-none-linux-gnueabihf --with-cpu=cortex-a9 works.
next prev parent reply other threads:[~2020-06-19 7:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 2:05 [Bug middle-end/95757] New: " seurer at linux dot vnet.ibm.com
2020-06-19 7:23 ` [Bug middle-end/95757] " rguenth at gcc dot gnu.org
2020-06-19 7:35 ` clyon at gcc dot gnu.org [this message]
2020-08-13 15:33 ` seurer at gcc dot gnu.org
2020-10-16 11:53 ` rguenth at gcc dot gnu.org
2020-10-16 12:03 ` clyon at gcc dot gnu.org
2020-12-16 18:14 ` seurer at gcc dot gnu.org
2021-02-23 2:59 ` hp at gcc dot gnu.org
2021-02-26 12:12 ` rguenth at gcc dot gnu.org
2021-03-01 14:48 ` jakub at gcc dot gnu.org
2021-03-01 17:59 ` jakub at gcc dot gnu.org
2021-03-02 10:49 ` cvs-commit at gcc dot gnu.org
2021-03-02 10:55 ` jakub 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-95757-4-OqyilU2za4@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).