public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/65752] Too strong optimizations int -> pointer casts
Date: Mon, 13 Apr 2015 17:38:00 -0000 [thread overview]
Message-ID: <bug-65752-4-ki6VUqQYRF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65752-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65752
--- Comment #1 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
On Mon, 13 Apr 2015, gcc at robbertkrebbers dot nl wrote:
> NB 1: I do not think that DR #260 applies here
Why not? It seems clear enough that optimizations based on pointer
origins are intended to be allowed; that it's not allowed to produce a
pointer based on another pointer out of thin air, because the
optimizations are more useful in practice than code such as this.
next prev parent reply other threads:[~2015-04-13 17:38 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 14:04 [Bug c/65752] New: " gcc at robbertkrebbers dot nl
2015-04-13 17:38 ` joseph at codesourcery dot com [this message]
2015-04-13 23:25 ` [Bug c/65752] " gcc at robbertkrebbers dot nl
2015-04-13 23:25 ` gcc at robbertkrebbers dot nl
2015-04-14 8:39 ` rguenth at gcc dot gnu.org
2015-04-14 8:46 ` gcc at robbertkrebbers dot nl
2015-04-14 9:01 ` rguenth at gcc dot gnu.org
2015-04-14 9:06 ` rguenth at gcc dot gnu.org
2015-04-14 9:23 ` gcc at robbertkrebbers dot nl
2015-04-14 9:26 ` gcc at robbertkrebbers dot nl
2015-04-14 10:50 ` rguenth at gcc dot gnu.org
2015-04-20 13:45 ` [Bug tree-optimization/65752] " mpolacek at gcc dot gnu.org
2015-04-20 13:53 ` gcc at robbertkrebbers dot nl
2015-05-18 17:13 ` gil.hur at sf dot snu.ac.kr
2015-05-19 9:21 ` rguenth at gcc dot gnu.org
2015-05-19 12:08 ` gil.hur at sf dot snu.ac.kr
2015-05-19 12:33 ` rguenth at gcc dot gnu.org
2015-05-19 13:14 ` gil.hur at sf dot snu.ac.kr
2015-05-19 14:21 ` rguenther at suse dot de
2015-05-19 14:29 ` gil.hur at sf dot snu.ac.kr
2015-05-19 14:32 ` mpolacek at gcc dot gnu.org
2015-05-19 15:12 ` gil.hur at sf dot snu.ac.kr
2015-05-19 15:23 ` Andreas Schwab
2015-05-19 15:23 ` schwab at suse dot de
2015-05-19 15:29 ` gil.hur at sf dot snu.ac.kr
2015-05-20 8:01 ` rguenth at gcc dot gnu.org
2015-05-20 10:55 ` gil.hur at sf dot snu.ac.kr
2015-05-20 11:20 ` gil.hur at sf dot snu.ac.kr
2015-05-20 11:33 ` rguenther at suse dot de
2015-05-22 4:55 ` mail at robbertkrebbers dot nl
2015-05-22 4:57 ` gcc at robbertkrebbers dot nl
2015-05-22 8:52 ` rguenth at gcc dot gnu.org
2015-05-23 8:14 ` gil.hur at sf dot snu.ac.kr
2015-05-26 11:26 ` rguenther at suse dot de
2015-05-26 13:55 ` gil.hur at sf dot snu.ac.kr
2015-05-26 14:00 ` rguenther at suse dot de
2015-05-26 14:06 ` gil.hur at sf dot snu.ac.kr
2020-08-04 21:31 ` tavianator at gmail dot com
2020-08-05 7:07 ` rguenther at suse dot de
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-65752-4-ki6VUqQYRF@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).