public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/53045] Missing loop termination
Date: Fri, 20 Apr 2012 16:14:00 -0000 [thread overview]
Message-ID: <bug-53045-4-Klx8QUrFse@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53045-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53045
--- Comment #3 from Uros Bizjak <ubizjak at gmail dot com> 2012-04-20 16:13:49 UTC ---
(In reply to comment #2)
> Btw, see how I fixed
>
> 2012-04-18 Richard Guenther <rguenther@suse.de>
>
> * gcc.target/x86_64/abi/test_passing_unions.c: Avoid undefined
> array access.
> * gcc.target/x86_64/abi/test_passing_structs.c: Likewise.
> * gcc.target/i386/avx256-unaligned-load-4.c: Fix array sizes.
>
> I suppose I didn't see the AVX fails because my testing box doesn't have AVX.
Thanks, I have fixed AVX testcases in the same way.
prev parent reply other threads:[~2012-04-20 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 17:00 [Bug tree-optimization/53045] New: " ubizjak at gmail dot com
2012-04-20 9:23 ` [Bug tree-optimization/53045] " rguenth at gcc dot gnu.org
2012-04-20 9:24 ` rguenth at gcc dot gnu.org
2012-04-20 16:14 ` ubizjak at gmail dot com [this message]
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-53045-4-Klx8QUrFse@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).