public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "geoffk at geoffk dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/25140] aliases, including weakref, break alias analysis
Date: Mon, 28 Nov 2005 19:22:00 -0000	[thread overview]
Message-ID: <20051128192227.19241.qmail@sourceware.org> (raw)
In-Reply-To: <bug-25140-638@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from geoffk at geoffk dot org  2005-11-28 19:22 -------
Subject: Re:  aliases, including weakref, break alias analysis


On 28/11/2005, at 10:40 AM, aoliva at gcc dot gnu dot org wrote:

> ------- Comment #2 from aoliva at gcc dot gnu dot org  2005-11-28  
> 18:40 -------
> I'd change the testcase s/weakref/alias/, so as to make it clear  
> that the error
> has nothing to do with the newly-introduced weakref, but rather  
> with regular
> aliases, that weakref builds upon.

If you do that, it won't work on Darwin, because Darwin doesn't have  
aliases.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25140


  parent reply	other threads:[~2005-11-28 19:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-28 17:03 [Bug middle-end/25140] New: " geoffk at gcc dot gnu dot org
2005-11-28 17:06 ` [Bug middle-end/25140] " pinskia at gcc dot gnu dot org
2005-11-28 18:40 ` aoliva at gcc dot gnu dot org
2005-11-28 19:22 ` geoffk at geoffk dot org [this message]
2005-11-29 13:55 ` aoliva at gcc dot gnu dot org
2005-11-30  1:01 ` geoffk at geoffk dot org
2009-09-26 11:29 ` rguenth at gcc dot gnu dot org
2009-09-26 11:51 ` geoffk at gcc dot gnu dot org
2009-09-26 12:01 ` rguenth at gcc dot gnu dot org
2009-09-26 12:15 ` geoffk at gcc dot gnu dot org
2010-05-09 16:50 ` rguenth at gcc dot gnu dot org
2010-08-13 20:11 ` bigotp at acm dot org
     [not found] <bug-25140-4@http.gcc.gnu.org/bugzilla/>
2014-02-17 12:25 ` rguenth at gcc dot gnu.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=20051128192227.19241.qmail@sourceware.org \
    --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).