public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Glas <wolfgang.glas@ev-i.at>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: target/9941: [HP-UX] typeinfo not generated correctly when #pragmas are involved
Date: Fri, 16 May 2003 07:16:00 -0000	[thread overview]
Message-ID: <20030516071601.9073.qmail@sources.redhat.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]

The following reply was made to PR target/9941; it has been noted by GNATS.

From: Wolfgang Glas <wolfgang.glas@ev-i.at>
To: gcc-prs@gcc.gnu.org, struppi@acm.org, gcc-bugs@gcc.gnu.org,
   gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org
Cc:  
Subject: Re: target/9941: [HP-UX] typeinfo not generated correctly when #pragmas are involved
Date: Fri, 16 May 2003 09:15:20 +0200

 Hi all,
 
   I just came across the same problem as described in the PR
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9941
 
 on another platform, namely
 
 gcc -v
 Reading specs from /usr/local/lib/gcc-lib/powerpc-ibm-aix4.3.3.0/3.2.3/specs
 Configured with: ./configure
 Thread model: aix
 gcc version 3.2.3
 
 So, I'd guess the bug might be present on all platforms which don't support
 weak symbols.
 
    lg,
 
      Wolfgang
 
 -- 
 Dr. Wolfgang Glas                         EV-i Informationstechnologie GmbH.
 Geschäftsführer                           Sebastian-Kneipp-Weg 17
 Wolfgang.Glas@ev-i.at                     A-6020 Innsbruck/Austria
 phone: +43-512-284883-2 +43-699-12665927  fax: +43-512-281624-31


                 reply	other threads:[~2003-05-16  7:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030516071601.9073.qmail@sources.redhat.com \
    --to=wolfgang.glas@ev-i.at \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).