public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/101242] Segfault in SLP vectorizor after g:2ad71efb5de
Date: Tue, 29 Jun 2021 07:51:42 +0000 [thread overview]
Message-ID: <bug-101242-4-tpF3ghvCkl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101242-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101242
--- Comment #6 from David Binderman <dcb314 at hotmail dot com> ---
(In reply to David Binderman from comment #4)
> Created attachment 51078 [details]
> gzipped C++ source code
>
> I also see this with -O3 with the attached C++ code.
Poor example - too big to reduce easily. Here is some reduced
C code from a different example:
--- /home/dcb/cvise/test/bug733b.c ---
typedef struct {
int height, width
} ufraw_image_data;
typedef struct {
ufraw_image_data thumb
} ufraw_data;
ufraw_data ufraw_convert_embedded_uf;
int ufraw_convert_embedded_uf_1;
void ufraw_convert_embedded(void) {
unsigned srcHeight = ufraw_convert_embedded_uf.thumb.height,
srcWidth = ufraw_convert_embedded_uf.thumb.width;
int scaleDenom = 1;
srcSize();
if (ufraw_convert_embedded_uf_1)
scaleDenom = srcSize;
unsigned dstWidth = srcWidth / scaleDenom;
unsigned dstHeight = srcHeight / scaleDenom;
if (dstWidth != srcWidth || dstHeight != srcHeight) {
unsigned width = dstHeight;
dstHeight = dstWidth;
dstWidth = width;
}
ufraw_convert_embedded_uf.thumb.height = dstHeight;
ufraw_convert_embedded_uf.thumb.width = dstWidth;
}
next prev parent reply other threads:[~2021-06-29 7:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 13:30 [Bug tree-optimization/101242] New: Segfault in SLP vectorizor after 2ad71efb5de jamborm at gcc dot gnu.org
2021-06-28 13:32 ` [Bug tree-optimization/101242] " jamborm at gcc dot gnu.org
2021-06-28 13:34 ` [Bug tree-optimization/101242] Segfault in SLP vectorizor after g:2ad71efb5de marxin at gcc dot gnu.org
2021-06-28 17:32 ` jamborm at gcc dot gnu.org
2021-06-28 21:40 ` dcb314 at hotmail dot com
2021-06-29 7:06 ` rguenth at gcc dot gnu.org
2021-06-29 7:51 ` dcb314 at hotmail dot com [this message]
2021-06-29 8:35 ` cvs-commit at gcc dot gnu.org
2021-06-29 8:35 ` rguenth at gcc dot gnu.org
2021-06-29 8:36 ` 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-101242-4-tpF3ghvCkl@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).