public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "19373742 at buaa dot edu.cn" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/110282] Segmentation fault with specific optimizations
Date: Mon, 19 Jun 2023 10:05:26 +0000	[thread overview]
Message-ID: <bug-110282-4-KNwcKL89m8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110282-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from CTC <19373742 at buaa dot edu.cn> ---
(In reply to Richard Biener from comment #3)
> Confirmed behavior also with GCC 10, with -fno-bit-tests -fbit-tests
> -fno-ipa-modref -fipa-modref removed.
> 
> Can you please adjust your script to not pointlessly increase the command
> line
> by adding both positive and neagtive variants of an option?  Can you please
> try to reduce the set of arbitrary options that reproduce the issue?
> 
> 25kB garbage testcases are painfully enough to even look at.  Other fuzzing
> people manage to file bugs with < 100 lines of code and a command line that
> remotely makes sense.

Sorry for the long command lines. This issue can be reproduced with -O3
-fno-dce -fno-ipa-cp -fno-tree-dce -fno-tree-sink.

  parent reply	other threads:[~2023-06-19 10:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-16 11:01 [Bug c/110282] New: " 19373742 at buaa dot edu.cn
2023-06-16 11:02 ` [Bug c/110282] " 19373742 at buaa dot edu.cn
2023-06-17  6:52 ` [Bug middle-end/110282] " xry111 at gcc dot gnu.org
2023-06-19  6:43 ` rguenth at gcc dot gnu.org
2023-06-19 10:05 ` 19373742 at buaa dot edu.cn [this message]
2023-06-19 21:57 ` pinskia at gcc dot gnu.org
2023-06-30  9:25 ` 19373742 at buaa dot edu.cn
2023-06-30  9:30 ` xry111 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-110282-4-KNwcKL89m8@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).