public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sergiodj at sergiodj dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/102316] Unexpected stringop-overflow Warnings on POWER CPU Date: Fri, 12 Aug 2022 02:37:59 +0000 [thread overview] Message-ID: <bug-102316-4-D8kJO9Mb0Q@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102316-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102316 Sergio Durigan Junior <sergiodj at sergiodj dot net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sergiodj at sergiodj dot net --- Comment #3 from Sergio Durigan Junior <sergiodj at sergiodj dot net> --- I can confirm this bug. We're facing the problem when compiling NSS on Ubuntu Kinetic (development version) on ppc64el, because the build uses -O3.
next prev parent reply other threads:[~2022-08-12 2:37 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-13 20:15 [Bug c/102316] New: " drc at linux dot vnet.ibm.com 2021-09-13 20:22 ` [Bug middle-end/102316] " pinskia at gcc dot gnu.org 2021-09-14 5:31 ` xtkoba at gmail dot com 2022-08-12 2:37 ` sergiodj at sergiodj dot net [this message] 2022-08-25 7:48 ` guihaoc at gcc dot gnu.org 2022-08-25 8:28 ` rguenth 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-102316-4-D8kJO9Mb0Q@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: linkBe 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).