public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "wojtek.golf at interia dot pl" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/60028] TIC6X: B3 register (return address) is saved on stack when real call is replaced with sibling call in a leaf function Date: Sun, 09 Feb 2014 00:24:00 -0000 [thread overview] Message-ID: <bug-60028-4-fdUIURorKf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60028-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60028 Wojciech Migda <wojtek.golf at interia dot pl> changed: What |Removed |Added ---------------------------------------------------------------------------- Target| |tic6x-none-elf Host| |Linux wmigda-desktop | |3.11.0-13-generic | |#20-Ubuntu SMP Wed Oct 23 | |17:26:33 UTC 2013 i686 i686 | |i686 GNU/Linux Version|4.8.2 |4.9.0 Build| |tic6x-none-elf-gcc (GCC) | |4.9.0 20140208 | |(experimental) --- Comment #1 from Wojciech Migda <wojtek.golf at interia dot pl> --- I have recreated the scenario on the latest 4.9.0 shanpshot, hence the changes in the headline/description. ================================================================================= Exact version of gcc: tic6x-none-elf-gcc (GCC) 4.9.0 20140208 (experimental) ================================================================================ System type: Linux wmigda-desktop 3.11.0-13-generic #20-Ubuntu SMP Wed Oct 23 17:26:33 UTC 2013 i686 i686 i686 GNU/Linux ================================================================================ Options given when gcc was built: export TRIPLET=tic6x-none-elf mkdir -pv ${X_BUILD_DIR}/gcc-${GCC_VER}-build-pass-1/ pushd ${X_BUILD_DIR}gcc-${GCC_VER}-build-pass-1/ && \ RANLIB_FOR_TARGET=${CXTOOLS}bin/${TRIPLET}-ranlib AS_FOR_TARGET=${CXTOOLS}bin/${TRIPLET}-as AR_FOR_TARGET=${CXTOOLS}bin/${TRIPLET}-ar \ AS=as AR=ar LDFLAGS='-lstdc++ -lm' ../../../../gcc/configure \ --prefix=${C_TOOLS} \ --build=$(gcc -dumpmachine) \ --host=$(gcc -dumpmachine) \ --target=${TRIPLET} \ --with-local-prefix=${CXTOOLS}${TRIPLET}/sysroot \ --with-sysroot=${CXTOOLS}${TRIPLET}/sysroot \ --disable-nls \ --disable-shared \ --without-headers \ --with-newlib \ --disable-decimal-float \ --disable-libgomp \ --disable-libmudflap \ --disable-libssp \ --disable-libatomic \ --disable-libquadmath \ --disable-threads \ --enable-languages=c \ --disable-multilib \ --with-mpfr=${C_TOOLS} \ --with-gmp=${C_TOOLS} \ --disable-__cxa_atexit \ --disable-sjlj-exceptions \ --enable-target-optspace \ --disable-libstdcxx-pch \ ; popd ================================================================================ Commandline: tic6x-none-elf-gcc -fleading-underscore -march=c674x -O2 -g0 -S main.c ================================================================================ Compiler output: nothing one the console ================================================================================ Preprocessed file: # 1 "main.c" # 1 "<command-line>" # 1 "main.c" int e_fun(int arg); extern int e_int; void g_fun(void) { e_fun(e_int); } ================================================================================
parent reply other threads:[~2014-02-09 0:24 UTC|newest] Thread overview: expand[flat|nested] mbox.gz Atom feed [parent not found: <bug-60028-4@http.gcc.gnu.org/bugzilla/>]
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-60028-4-fdUIURorKf@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: linkBe 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).