public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Toon Moene <toon@moene.indiv.nluug.nl>
To: Toon Moene <toon@moene.indiv.nluug.nl>
Cc: Daniel Berlin <dberlin@dberlin.org>,
	"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	Diego Novillo <dnovillo@redhat.com>
Subject: Re: [tree-ssa] Fix bootstrap failure
Date: Sun, 30 Nov 2003 19:31:00 -0000	[thread overview]
Message-ID: <3FCA4162.2040208@moene.indiv.nluug.nl> (raw)
In-Reply-To: <3FCA3D3A.7020305@moene.indiv.nluug.nl>

Toon Moene wrote:

> Daniel Berlin wrote:
> 
>> On Nov 30, 2003, at 1:33 PM, Toon Moene wrote:

>>> Talking about "fixed" - as far as I can see your PTA only takes 
>>> effect if HAVE_BANSHEE is defined during compilation.

>> Because it gets thrown into gcc's config.h.

> Yep, got it - was looking in the wrong spot.  Sorry.

BTW, the real reason I'm interested in alias analysis is to implement 
Fortran's "if you don't tell us you're not aliasing" rules.

I'm looking at tree-alias-common.c (intra_function_call):

   /* We assume that an actual parameter can point to any global. */

where Fortran would change the "can" to "cannot" :-)

Is that the point to change ?

Thanks in advance,



-- 
Toon Moene - mailto:toon@moene.indiv.nluug.nl - phoneto: +31 346 214290
Saturnushof 14, 3738 XG  Maartensdijk, The Netherlands
Maintainer, GNU Fortran 77: http://gcc.gnu.org/onlinedocs/g77_news.html
GNU Fortran 95: http://gcc.gnu.org/fortran/ (under construction)

  reply	other threads:[~2003-11-30 19:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-30 15:11 Diego Novillo
2003-11-30 15:51 ` Daniel Berlin
2003-11-30 19:09   ` Toon Moene
2003-11-30 19:10     ` Daniel Berlin
2003-11-30 19:12       ` Toon Moene
2003-11-30 19:31         ` Toon Moene [this message]
2003-11-30 19:56           ` Daniel Berlin
2003-11-30 21:01             ` Toon Moene

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=3FCA4162.2040208@moene.indiv.nluug.nl \
    --to=toon@moene.indiv.nluug.nl \
    --cc=dberlin@dberlin.org \
    --cc=dnovillo@redhat.com \
    --cc=gcc-patches@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).