public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/108402] False positive Wuninitialized with ftrivial-auto-var-init=pattern
Date: Sun, 15 Jan 2023 19:23:36 +0000	[thread overview]
Message-ID: <bug-108402-4-3n8MYLqmkI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108402-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to pefoley2 from comment #4)
> Yeah, I had a lot of trouble getting creduce to do something sane with the
> testcase that didn't wind up just deleting everything.

You could compress it using either bzip or gzip (or xz). We are ok with the
file being compressed if it goes over the attachment size limit.

> It should also be reproducible via make O=um ARCH=um allyesconfig
> drivers/spi/spi-stm32-qspi.o in a 6.1 linux kernel tree.
from https://gcc.gnu.org/bugs/ (What we do not want):
```
The location (URL) of the package that failed to build (we won't download it,
anyway, since you've already given us what we need to duplicate the bug,
haven't you? :-)
```

  parent reply	other threads:[~2023-01-15 19:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-14  5:42 [Bug c/108402] New: " pefoley2 at pefoley dot com
2023-01-14  5:49 ` [Bug tree-optimization/108402] " pinskia at gcc dot gnu.org
2023-01-14  6:56 ` pinskia at gcc dot gnu.org
2023-01-15 18:46 ` pefoley2 at pefoley dot com
2023-01-15 18:51 ` pefoley2 at pefoley dot com
2023-01-15 19:23 ` pinskia at gcc dot gnu.org [this message]
2023-01-16 22:47 ` pefoley2 at pefoley dot com
2023-07-19 16:03 ` arnd at linaro dot 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-108402-4-3n8MYLqmkI@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).