public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ro@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, kreckel@ginac.de,
	nobody@gcc.gnu.org, ro@TechFak.Uni-Bielefeld.DE, ro@gcc.gnu.org
Subject: Re: target/5505: Doubts about a patch for OSF
Date: Wed, 30 Jan 2002 06:14:00 -0000	[thread overview]
Message-ID: <20020130141419.19237.qmail@sources.redhat.com> (raw)

Synopsis: Doubts about a patch for OSF

Responsible-Changed-From-To: unassigned->ro
Responsible-Changed-By: ro
Responsible-Changed-When: Wed Jan 30 06:14:19 2002
Responsible-Changed-Why:
    Mine.
State-Changed-From-To: open->feedback
State-Changed-By: ro
State-Changed-When: Wed Jan 30 06:14:19 2002
State-Changed-Why:
    Please follow the bug reporting instructions at
    
    	http://gcc.gnu.org/bugs.html
    
    and include all the required information (especially how GCC
    was configured and a self-contained test case).  Without a
    testcase demonstrating the problem, I cannot reproduce or
    fix this.  as, ar, or nm messages out of context (i.e.
    without the corresponding source files) don't help here.
    
    Besides, I've been able to build and test CLN 1.1.4 on
    alpha-dec-osf5.1 with a copy a gcc 3.0.2 prerelease without
    any problems, i.e. make and make check both complete
    sucessfully.
    
    The problem may therefore be due not to a gcc problem but
    to a as or ld bug.  The machine used here is running
    Tru64 UNIX V5.1 with Patch Kit 3 installed.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5505


             reply	other threads:[~2002-01-30 14:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-30  6:14 ro [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-10  5:36 Rainer Orth
2002-05-10  5:27 ro
2002-05-09 10:56 Richard B. Kreckel
2002-04-16 10:56 Rainer Orth
2002-02-25  8:58 Rainer Orth
2002-02-23 14:12 Richard B. Kreckel
2002-02-22 15:46 Rainer Orth
2002-02-22 14:16 Rainer Orth
2002-02-21 16:21 Richard B. Kreckel
2002-02-20  9:36 Richard B. Kreckel
2002-02-19  5:26 Rainer Orth
2002-02-18 12:56 Richard B. Kreckel
2002-02-04 11:06 Rainer Orth
2002-02-04 11:06 Richard B. Kreckel
2002-01-27  6:26 kreckel

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=20020130141419.19237.qmail@sources.redhat.com \
    --to=ro@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=kreckel@ginac.de \
    --cc=nobody@gcc.gnu.org \
    --cc=ro@TechFak.Uni-Bielefeld.DE \
    /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).