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 go/60874] FAIL: go.test/test/recover.go execution
Date: Wed, 06 Aug 2014 13:03:00 -0000 [thread overview]
Message-ID: <bug-60874-4-Z48dav8ZJb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60874-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60874
--- Comment #9 from Uroš Bizjak <ubizjak at gmail dot com> ---
To illustrate unreliable approach, please compile following test:
--cut here--
extern void foo (void *);
int test(void)
{
__label__ bla;
foo (&&bla);
bla:
return 0;
}
--cut here--
gcc -O2:
test:
.L2:
pushl %ebp
movl %esp, %ebp
subl $8, %esp
movl $.L2, (%esp)
call foo
xorl %eax, %eax
leave
ret
The passed argument doesn't represent return address.
>From gcc-bugs-return-457871-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Aug 06 13:11:31 2014
Return-Path: <gcc-bugs-return-457871-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18464 invoked by alias); 6 Aug 2014 13:11:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 18441 invoked by uid 48); 6 Aug 2014 13:11:28 -0000
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61749] arm_neon.h "_lane" and "_n" intrinsics can cause ICEs
Date: Wed, 06 Aug 2014 13:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 4.8.4
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ktkachov at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jgreenhalgh at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-61749-4-bMIzIDjcEH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61749-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61749-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-08/txt/msg00368.txt.bz2
Content-length: 819
https://gcc.gnu.org/bugzilla/show_bug.cgi?ida749
--- Comment #3 from ktkachov at gcc dot gnu.org ---
vqdmlal_lane_s16 expects an immediate/literal lane number as the fourth
argument and the builtin expansion code in aarch64-builtins.c is actually
equipped to error out when given a variable (in the SIMD_ARG_CONSTANT case of
aarch64_simd_expand_args).
However the type qualifiers for vqdmlal_lane_s16 are the QUADOP qualifiers
which don't enforce qualifier_immediate on the builtin, thus falling into the
SIMD_ARG_COPY_TO_REG and later on failing the CONST_INT_P assert when
processing the lane numbers.
If I give qualifier_immediate to the 4th argument I get a more helpful:
error: incompatible type for argument 4, expected 'const int'
message but the compiler still tries to proceed and ends up ICEing anyway.
next prev parent reply other threads:[~2014-08-06 13:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 18:14 [Bug go/60874] New: " ubizjak at gmail dot com
2014-07-20 8:27 ` [Bug go/60874] " ubizjak at gmail dot com
2014-07-20 9:12 ` ian at airs dot com
2014-07-21 12:31 ` ubizjak at gmail dot com
2014-07-21 14:35 ` ubizjak at gmail dot com
2014-08-05 14:09 ` ian at airs dot com
2014-08-05 14:14 ` ubizjak at gmail dot com
2014-08-06 13:00 ` ubizjak at gmail dot com
2014-08-06 13:03 ` ubizjak at gmail dot com [this message]
2014-08-06 13:12 ` schwab@linux-m68k.org
2014-08-06 13:27 ` ubizjak at gmail dot com
2014-08-06 13:56 ` ian at airs dot com
2014-08-06 14:17 ` ubizjak at gmail dot com
2014-08-06 17:16 ` ubizjak at gmail dot com
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-60874-4-Z48dav8ZJb@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).