public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "chipitsine at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/106297] stringop-overflow misbehaviour on atomic
Date: Fri, 15 Jul 2022 02:33:26 +0000	[thread overview]
Message-ID: <bug-106297-4-9DAiPEFTUq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106297-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106297

--- Comment #2 from Илья Шипицин <chipitsine at gmail dot com> ---
I have provided repro steps, hope they can be used to find any answer.

I tried to add "-save-temps", but it gave another error (not seen without that
option):

  CC      src/slz.o
In file included from src/slz.c:29:
include/import/slz-tables.h: In function ‘dist_to_code’:
include/import/slz-tables.h:182:35: error: this statement may fall through
[-Werror=implicit-fallthrough=]
  182 |         case 24577 ... 32768: code++; /* fall through */
      |                               ~~~~^~
compilation terminated due to -Wfatal-errors.
cc1: all warnings being treated as errors
make: *** [Makefile:1004: src/slz.o] Error 1

  parent reply	other threads:[~2022-07-15  2:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-14 14:05 [Bug c/106297] New: " chipitsine at gmail dot com
2022-07-14 16:05 ` [Bug tree-optimization/106297] " pinskia at gcc dot gnu.org
2022-07-15  2:33 ` chipitsine at gmail dot com [this message]
2022-07-15  8:05 ` [Bug tree-optimization/106297] [12/13 Regression] stringop-overflow misbehaviour on atomic since r12-4725-g88b504b7a8c5affb marxin at gcc dot gnu.org
2022-07-15  8:05 ` marxin at gcc dot gnu.org
2022-07-18  7:27 ` rguenth at gcc dot gnu.org
2022-07-25 15:03 ` rguenth at gcc dot gnu.org
2022-07-28 14:33 ` jakub at gcc dot gnu.org
2022-07-28 15:28 ` msebor at gcc dot gnu.org
2023-05-08 12:25 ` [Bug tree-optimization/106297] [12/13/14 " 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-106297-4-9DAiPEFTUq@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).