public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dannysmith at users dot sourceforge dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/33946] New: Testcase multi-ix.c generates call to (poisoned) bzero Date: Tue, 30 Oct 2007 00:30:00 -0000 [thread overview] Message-ID: <bug-33946-4066@http.gcc.gnu.org/bugzilla/> (raw) testsuite gcc.c-torture/execute/multi-ix.c calls __builtin_bzero; At -O0, this gets expanded to a libcall to non-ISO function bzero mingw32 does not have a library function bzero.. Hence: spawn /develop/svn/trunk/build/gcc/xgcc -B/develop/svn/trunk/build/gcc/ /develop/svn/trunk/src/gcc/testsuite/gcc.c-torture/execute/multi-ix.c -w -O0 -fno-show-column -lm -o /develop/svn/trunk/build/gcc/testsuite/gcc/multi-ix.x0 c:\tmp/ccsxRYXw.o:multi-ix.c:(.text+0x9a3): undefined reference to `_bzero' Why not use ___builtin_memset in the testcase instead of poisoned name ? -- Summary: Testcase multi-ix.c generates call to (poisoned) bzero Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: testsuite AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: dannysmith at users dot sourceforge dot net GCC target triplet: i686-pc-mingw32 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33946
next reply other threads:[~2007-10-30 0:30 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-10-30 0:30 dannysmith at users dot sourceforge dot net [this message] 2007-11-19 5:05 ` [Bug testsuite/33946] " pinskia at gcc dot gnu dot org 2008-01-30 10:08 ` fxcoudert at gcc dot gnu dot org 2008-02-05 12:04 ` fxcoudert at gcc dot gnu dot org 2008-02-05 12:05 ` fxcoudert at gcc dot gnu dot 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-33946-4066@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).