From: torbenh <torbenh@gmx.de>
To: gcc@gcc.gnu.org
Subject: Re: adding -fnoalias ... would a patch be accepted ?
Date: Wed, 06 Jan 2010 17:37:00 -0000 [thread overview]
Message-ID: <20100106173720.GH20987@siel.b> (raw)
In-Reply-To: <84fc9c001001060745i3cc75b27vc011c6b15eee0eaf@mail.gmail.com>
On Wed, Jan 06, 2010 at 04:45:06PM +0100, Richard Guenther wrote:
> >> I don't see a restrict qualified pointer here. Â Note that the
> >> restrict attribute would only disambiguate against those.
> >> Also I think you need the restrict attribute on the Mixer
> >> objects, not its members.
> >
> > so the attribute would promote down to all member vars of
> > member objects ?
>
> Yes. In fact the example above would work I guess.
confirmed. works nicely.
although it would be nice, if this would also
apply to FIELD_DECL.
i am not sure if this is really possible.
is the structure hierarchy still available at that layer ?
thanks for your help so far.
>
> >
> >> > i still dont understand whats the problem with -fnolias,
> >> > as in attached patch.
> >>
> >> The patch will miscompile everything.
> >
> > point taken.
> > obviously reading code for a few hours without knowing enough about the
> > code isnt enough :)
> >
> > __attribute__((restrict)) is the better solution.
> > although not portable to other compilers.
> >
> > but i need this kind of functionality now, to test my concepts.
> > thats why i am spending a bit time on this.
> >
> > when do you plan to add this feature ?
>
> For GCC 4.6 earliest.
hmm... bah :)
--
torben Hohn
prev parent reply other threads:[~2010-01-06 17:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 13:40 torbenh
2010-01-05 13:46 ` Richard Guenther
2010-01-05 15:02 ` torbenh
2010-01-05 16:42 ` Tim Prince
2010-01-05 15:03 ` torbenh
2010-01-05 15:27 ` Richard Guenther
2010-01-05 16:39 ` torbenh
2010-01-06 13:27 ` Richard Guenther
2010-01-06 15:26 ` torbenh
2010-01-06 15:45 ` torbenh
2010-01-06 15:51 ` Richard Guenther
2010-01-06 15:45 ` Richard Guenther
2010-01-06 15:49 ` Richard Guenther
2010-01-06 16:48 ` torbenh
2010-01-06 17:37 ` torbenh [this message]
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=20100106173720.GH20987@siel.b \
--to=torbenh@gmx.de \
--cc=gcc@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).