public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hoogerbrugge at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/14192] Restrict pointers don't help
Date: Wed, 18 Feb 2004 15:33:00 -0000	[thread overview]
Message-ID: <20040218153336.19411.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040218135530.14192.hoogerbrugge@hotmail.com>


------- Additional Comments From hoogerbrugge at hotmail dot com  2004-02-18 15:33 -------
I just did a update to version 3.5.0 20040218 and the problem is still there.

Are you not able to reproduce it because you don't have the sources of the my 
target port? If so, should I sent sources of the port?


-- 


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


  parent reply	other threads:[~2004-02-18 15:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-18 13:55 [Bug middle-end/14192] New: " hoogerbrugge at hotmail dot com
2004-02-18 14:11 ` [Bug middle-end/14192] " pinskia at gcc dot gnu dot org
2004-02-18 14:15 ` pinskia at gcc dot gnu dot org
2004-02-18 15:33 ` hoogerbrugge at hotmail dot com [this message]
2004-02-19 14:02 ` hoogerbrugge at hotmail dot com
2004-10-11 10:56 ` giovannibajo at libero dot it
2005-01-23 18:48 ` steven at gcc dot gnu dot org
2005-01-23 18:51 ` steven at gcc dot gnu dot org
2005-01-23 20:59 ` joseph at codesourcery dot com
2005-09-28  5:21 ` ian at airs dot com
     [not found] <bug-14192-7804@http.gcc.gnu.org/bugzilla/>
2007-06-11  0:34 ` pinskia at gcc dot gnu dot org
2008-10-01 14:29 ` rguenth at gcc dot gnu dot org
2010-04-27 18:09 ` pinskia at gcc dot gnu dot org
2010-04-28 15:53 ` alexey dot salmin at gmail dot com
     [not found] <bug-14192-4@http.gcc.gnu.org/bugzilla/>
2013-06-26 16:16 ` colanderman at gmail dot com

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=20040218153336.19411.qmail@sources.redhat.com \
    --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).