public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/107387] [13 Regression] gcc trunk -O2 crashes when enable UBSan since r13-2288-g61c4c989034548
Date: Tue, 25 Oct 2022 09:06:36 +0000	[thread overview]
Message-ID: <bug-107387-4-OdPF6DQjBV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107387-4@http.gcc.gnu.org/bugzilla/>

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

rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|unassigned at gcc dot gnu.org      |rsandifo at gcc dot gnu.org

--- Comment #3 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
Mine.

  parent reply	other threads:[~2022-10-25  9:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-24 20:38 [Bug c/107387] New: gcc trunk -O2 crashes when enable UBSan shaohua.li at inf dot ethz.ch
2022-10-24 20:42 ` [Bug c/107387] [13 Regression] " mpolacek at gcc dot gnu.org
2022-10-24 20:44 ` [Bug tree-optimization/107387] " mpolacek at gcc dot gnu.org
2022-10-25  7:01 ` [Bug tree-optimization/107387] [13 Regression] gcc trunk -O2 crashes when enable UBSan since r13-2288-g61c4c989034548 rguenth at gcc dot gnu.org
2022-10-25  9:06 ` rsandifo at gcc dot gnu.org [this message]
2022-10-26  9:07 ` rsandifo 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-107387-4-OdPF6DQjBV@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).