public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/8829: Over-optimization at -O2 and above (affecting GLIBC macros) Date: Thu, 05 Dec 2002 14:46:00 -0000 [thread overview] Message-ID: <20021205224602.29400.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/8829; it has been noted by GNATS. From: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de> To: bagnara@cs.unipr.it Cc: gcc-gnats@gcc.gnu.org, abramo.bagnara@libero.it Subject: Re: optimization/8829: Over-optimization at -O2 and above (affecting GLIBC macros) Date: 05 Dec 2002 23:41:02 +0100 bagnara@cs.unipr.it writes: > With -O2, gcc removes instructions that should not be removed. > >How-To-Repeat: > Compile the attached file, bug.cc, with > $ gcc -S -O2 bug.c > and notice that the instructions for swapping the bytes > have been removed from get_float32() while, interestingly, > they have not been removed from get_int32(). > Notice also that, if the call to q(v) is uncommented from > get_float32(), the over-optimization goes away. [...] > static inline void swap_float32(float* p) > { > *(int*)p = __bswap_32(*(int*)p); > } Looks to me like this violates aliasing rules, and indeed -fno-strict-aliasing keeps the asm. -- Falk
next reply other threads:[~2002-12-05 22:46 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-05 14:46 Falk Hueffner [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-12-10 14:22 bangerth 2002-12-05 13:26 bagnara
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=20021205224602.29400.qmail@sources.redhat.com \ --to=falk.hueffner@student.uni-tuebingen.de \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).