public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ljrittle@gcc.gnu.org
To: Sylvain.Pion@sophia.inria.fr, gcc-bugs@gcc.gnu.org,
	gcc-prs@gcc.gnu.org, ljrittle@gcc.gnu.org, nobody@gcc.gnu.org
Subject: Re: libstdc++/3195: STL warning on Solaris with GCC 3.0
Date: Fri, 15 Jun 2001 16:03:00 -0000	[thread overview]
Message-ID: <20010615230314.28249.qmail@sourceware.cygnus.com> (raw)

Synopsis: STL warning on Solaris with GCC 3.0

Responsible-Changed-From-To: unassigned->ljrittle
Responsible-Changed-By: ljrittle
Responsible-Changed-When: Fri Jun 15 16:03:14 2001
Responsible-Changed-Why:
    Non-fatal issue related to one of my recent patches.
State-Changed-From-To: open->analyzed
State-Changed-By: ljrittle
State-Changed-When: Fri Jun 15 16:03:14 2001
State-Changed-Why:
    This issue is not seen on solaris2.7 (the Solaris
    platform used to test).  Here is representative
    key difference between preprocessed files:
    solaris2.7:
    <       __gthread_mutex_t __tmp = {{{0}, 0}, {{{0}}}, {0}};
    solaris2.6:
    >       __gthread_mutex_t __tmp = {0, 0, 0};
    
    Alex mentioned that older Solaris headers might need
    a fix up.  The solution is to add a pthread.h fixup to
    inclhack.def similar to solaris27_mutex_init.  I
    will write a proposed fixup and sent it to Sylvain
    for testing.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3195&database=gcc


             reply	other threads:[~2001-06-15 16:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-15 16:03 ljrittle [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-06 14:57 bangerth
2002-11-06 14:56 Wolfgang Bangerth
2002-11-06 14:46 Phil Edwards
2002-11-06  9:20 bangerth
2002-03-28 16:16 Phil Edwards
2002-03-28 15:44 bkoz
2001-06-25 22:42 ljrittle
2001-06-15  6:26 Sylvain Pion

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=20010615230314.28249.qmail@sourceware.cygnus.com \
    --to=ljrittle@gcc.gnu.org \
    --cc=Sylvain.Pion@sophia.inria.fr \
    --cc=gcc-bugs@gcc.gnu.org \
    --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).