public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Jeff Donner <jdonner@schedsys.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: target/5383: 3.0.3 with threads enabled links with unsatisfied thread symbols, even with -threads
Date: Tue, 15 Jan 2002 08:06:00 -0000	[thread overview]
Message-ID: <20020115160602.9015.qmail@sources.redhat.com> (raw)

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

From: Jeff Donner <jdonner@schedsys.com>
To: rodrigc@gcc.gnu.org, jdonner@schedsys.com, nobody@gcc.gnu.org,
	gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: target/5383: 3.0.3 with threads enabled links with unsatisfied thread symbols, even with -threads
Date: Tue, 15 Jan 2002 11:00:59 -0500

 > Synopsis: 3.0.3 with threads enabled links with unsatisfied thread symbols, even with -threads
 
 >     Duplicate of PR 3314, see:
 
 
 >     http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=3314
 > 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5383
 
 
 I don't think it's a duplicate of 3314;  unlike 3314 I explicitly 
 specify --enable-threads=posix, and indeed the resulting gcc -v says:
 
 ...
 
 Thread model: posix
 gcc version 3.0.3
 
 
 3314 is about how if you just say --enable-threads
 it may default to no threads.  5383 shows details of how the thread 
 support is bad, when you do get it (by asking explicitly).
 
 Unless you mean, '3314 and 5383 both show that thread support is messed 
 up on hp 11'.  However, I think 5383 has more helpful detail, enough to 
 be worth keeping.  3314 just shows an indirect stumble over the fact 
 that something is wrong.
 
 Jeff
 


             reply	other threads:[~2002-01-15 16:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-15  8:06 Jeff Donner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-14 19:12 rodrigc
2002-01-14 13:06 jdonner

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=20020115160602.9015.qmail@sources.redhat.com \
    --to=jdonner@schedsys.com \
    --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).