public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "huangcunjian at huawei dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/66062] New: under O2 optimization level , aarch64 compiler give informance : internal compiler error: in expand_assignment, at expr.c:4838
Date: Fri, 08 May 2015 03:25:00 -0000 [thread overview]
Message-ID: <bug-66062-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66062
Bug ID: 66062
Summary: under O2 optimization level , aarch64 compiler give
informance : internal compiler error: in
expand_assignment, at expr.c:4838
Product: gcc
Version: 4.9.3
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: huangcunjian at huawei dot com
Target Milestone: ---
Created attachment 35493
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35493&action=edit
testcase context
gcc version:
Target: aarch64-linux-gnu
Configured with:
/usr1/code/CODE_SDKV1R5C00/code/current/V1R5/build/script/cpu_hcc/p660/p660_build_dir/src/gcc-4.9/configure
--build=x86_64-suse-linux --host=x86_64-suse-linux --target=aarch64-linux-gnu
--with-arch=armv8-a
--prefix=/usr1/code/CODE_SDKV1R5C00/code/current/V1R5/build/script/cpu_hcc/p660/p660_build_dir/install
--disable-multilib --enable-__cxa_atexit --with-gnu-as --with-gnu-ld
--disable-libmudflap --disable-libgomp --disable-libssp --enable-threads
--enable-plugin --enable-c99 --enable-long-long --disable-nls --enable-shared
--enable-poison-system-directories --enable-symvers=gnu --with-pkgversion='SDK
V100R005C00B101' --enable-languages=c,c++
command:
aarch64-linux-gnu-gcc -w -O2 EMI_61144035_2_rd.i
compiler actual output :
./testsuite/gcc.target/hidsp/emi/20150428_151230_normal1/output/2015-4-29_6-46-13_17379704/EMI_61144035_2_rd.c:
In function 'func_1':
./testsuite/gcc.target/hidsp/emi/20150428_151230_normal1/output/2015-4-29_6-46-13_17379704/EMI_61144035_2_rd.c:747:56:
internal compiler error: in expand_assignment, at expr.c:4838
0x670942 expand_assignment(tree_node*, tree_node*, bool)
/usr1/code/CODE_SDKV1R5C00/code/current/V1R5/build/script/cpu_hcc/p660/p660_build_dir/src/gcc-4.9/gcc/expr.c:4838
0x5b4416 expand_gimple_stmt_1
/usr1/code/CODE_SDKV1R5C00/code/current/V1R5/build/script/cpu_hcc/p660/p660_build_dir/src/gcc-4.9/gcc/cfgexpand.c:3226
0x5b4a70 expand_gimple_stmt
/usr1/code/CODE_SDKV1R5C00/code/current/V1R5/build/script/cpu_hcc/p660/p660_build_dir/src/gcc-4.9/gcc/cfgexpand.c:3322
0x5b5588 expand_gimple_basic_block
/usr1/code/CODE_SDKV1R5C00/code/current/V1R5/build/script/cpu_hcc/p660/p660_build_dir/src/gcc-4.9/gcc/cfgexpand.c:5162
0x5b93b6 gimple_expand_cfg
/usr1/code/CODE_SDKV1R5C00/code/current/V1R5/build/script/cpu_hcc/p660/p660_build_dir/src/gcc-4.9/gcc/cfgexpand.c:5741
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.
next reply other threads:[~2015-05-08 3:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 3:25 huangcunjian at huawei dot com [this message]
2015-07-28 4:41 ` [Bug target/66062] " ssaraswati at gmail dot com
2015-07-28 6:22 ` trippels at gcc dot gnu.org
2015-07-28 10:20 ` ssaraswati at gmail dot com
2015-07-28 10:31 ` trippels 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-66062-4@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).