public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "filippo dot arcidiacono at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/30936] New: const attribute in nanf prototype causes gcc not producing correct code. Date: Fri, 23 Feb 2007 15:39:00 -0000 [thread overview] Message-ID: <bug-30936-14151@http.gcc.gnu.org/bugzilla/> (raw) Being nanf declared using const attribute, sh4-linux-gcc (4.1.1) doesn't produce the code to call the nanf function. Removing the 'const' attribute the generated code works fine. Using gcc (3.4.3) Red Hat EL4 the test runs fine. -- Summary: const attribute in nanf prototype causes gcc not producing correct code. Product: gcc Version: 4.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: filippo dot arcidiacono at gmail dot com GCC host triplet: i686-pc-linux-gnu GCC target triplet: sh4-linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30936
next reply other threads:[~2007-02-23 15:39 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-02-23 15:39 filippo dot arcidiacono at gmail dot com [this message] 2007-02-23 15:43 ` [Bug c/30936] " filippo dot arcidiacono at gmail dot com 2007-02-23 17:39 ` pinskia at gcc dot gnu dot org 2007-02-26 8:08 ` filippo dot arcidiacono at gmail dot com 2007-02-26 8:21 ` [Bug target/30936] " pinskia at gcc dot gnu dot org 2007-02-26 9:29 ` filippo dot arcidiacono at gmail dot com 2007-02-26 9:52 ` [Bug target/30936] __builtin_nanf("") != __builtin_nanf("") is false for sh4-linux-gnu pinskia at gcc dot gnu dot org 2007-02-26 13:01 ` filippo dot arcidiacono at gmail dot com 2007-02-26 18:02 ` pinskia 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-30936-14151@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).