public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Lev Assinovsky" <LAssinovsky@algorithm.aelita.com>
To: "Alexandre Oliva" <aoliva@redhat.com>
Cc: "Gcc-Bugs (E-mail)" <gcc-bugs@gcc.gnu.org>,
"Gcc-Help (E-mail)" <gcc-help@gcc.gnu.org>
Subject: RE: Is this a bug?
Date: Thu, 21 Aug 2003 09:23:00 -0000 [thread overview]
Message-ID: <3F6F4712B759A34ABD453A8B39C10D62DEE73B@bagman.edm.com> (raw)
The test case passed under gcc 3.3.1.
The problem was in lack of SOM weak support in gcc prior 3.3
----
Lev Assinovsky
Aelita Software Corporation
O&S Core Division, Programmer
ICQ# 165072909
> -----Original Message-----
> From: Alexandre Oliva [mailto:aoliva@redhat.com]
> Sent: Tuesday, August 12, 2003 10:57 PM
> To: Lev Assinovsky
> Cc: Gcc-Bugs (E-mail); Gcc-Help (E-mail)
> Subject: Re: Is this a bug?
>
>
> On Aug 12, 2003, "Lev Assinovsky"
> <LAssinovsky@algorithm.aelita.com> wrote:
>
> > gcc 3.2.3, HPUX-11.00:
>
> > t.cpp: In static member function `static const item* A::f()':
> > t.cpp:6: warning: sorry: semantics of inline function
> static data `const item
> > arr[1]' are wrong (you'll wind up with multiple copies)
> > t.cpp:6: warning: you can work around this by removing
> the initializer
>
> It's not as much of a bug, but rather a limitation AFAIK imposed by
> the object file of the platform you've chosen. GCC requires weak
> symbols in order to implement this feature correctly, and 32-bit HP-UX
> object files don't support them (completely?).
>
> --
> Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
> Red Hat GCC Developer aoliva@{redhat.com, gcc.gnu.org}
> CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
> Free Software Evangelist Professional serial bug killer
>
next reply other threads:[~2003-08-21 9:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-21 9:23 Lev Assinovsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-06 21:33 Matthew Toseland
2003-02-06 22:18 ` Falk Hueffner
2003-01-02 21:21 Songtao Chen
2003-01-02 21:24 ` Neil Booth
2003-01-02 21:42 ` Songtao Chen
2003-01-02 21:46 ` Neil Booth
2003-01-02 23:00 ` Songtao Chen
2003-01-13 5:17 ` Zack Weinberg
2003-01-13 5:17 ` Songtao Chen
2002-08-30 2:41 Ritzert
2002-09-03 14:07 ` Matt Austern
2002-09-10 1:06 ` Michael Ritzert
2000-12-06 3:42 Martin Kahlert
2000-01-30 16:44 Kuo Yu Chuang
[not found] <007d01bf6988$d2fb0c40$795d608c@ccl.itri.org.tw>
2000-01-30 2:45 ` Martin v. Loewis
1999-05-11 21:09 Christian II
1999-05-11 23:44 ` Martin v. Loewis
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=3F6F4712B759A34ABD453A8B39C10D62DEE73B@bagman.edm.com \
--to=lassinovsky@algorithm.aelita.com \
--cc=aoliva@redhat.com \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-help@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).