From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: Paolo Carlini <pcarlini@suse.de>
Cc: Jason Merrill <jason@redhat.com>,
Giovanni Bajo <giovannibajo@libero.it>,
Gerald Pfeifer <gp@suse.de>,
gcc@gcc.gnu.org, Andreas Jaeger <aj@suse.de>,
Nathanael Nerode <neroden@twcny.rr.com>
Subject: Re: pthread related breakage (mainline)
Date: Tue, 09 Dec 2003 01:48:00 -0000 [thread overview]
Message-ID: <m34qward79.fsf@uniton.integrable-solutions.net> (raw)
In-Reply-To: <3FD505BE.2070909@suse.de>
Paolo Carlini <pcarlini@suse.de> writes:
| Jason Merrill wrote:
|
| >I think it is--I think your overload patch broke it. The problem is that
| >the #pragma weaks for the pthread functions are now being ignored, because
| >handle_pragma_weak expects an affected function to be the
| >identifier_global_value of its name, and now it isn't.
| >
| Ah!
|
| *Many* thanks Jason and sorry Nathanael for having suspected your
| changes... I couldn't imagine an interaction between threads and the
| C++ front end, poor me...
Did you say good abstractions? ;-) :-)
-- Gaby
next prev parent reply other threads:[~2003-12-09 1:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-08 10:20 Gerald Pfeifer
2003-12-08 10:34 ` Eric Christopher
2003-12-08 12:12 ` Gerald Pfeifer
2003-12-08 12:47 ` Paolo Carlini
2003-12-08 12:57 ` Gerald Pfeifer
2003-12-08 13:02 ` Paolo Carlini
2003-12-08 13:16 ` Giovanni Bajo
2003-12-08 13:25 ` Paolo Carlini
2003-12-08 14:43 ` Giovanni Bajo
2003-12-08 23:15 ` Jason Merrill
2003-12-08 23:17 ` Jason Merrill
2003-12-09 4:05 ` Giovanni Bajo
2003-12-09 5:08 ` Jason Merrill
2003-12-09 19:09 ` Giovanni Bajo
2003-12-09 20:11 ` Jason Merrill
2003-12-08 23:31 ` Paolo Carlini
2003-12-09 1:48 ` Gabriel Dos Reis [this message]
2003-12-08 18:24 Giovanni Bajo
2003-12-08 18:24 ` Paolo Carlini
2003-12-08 18:48 ` Paolo Carlini
2003-12-08 18:59 ` Paolo Carlini
2003-12-08 19:25 ` Janis Johnson
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=m34qward79.fsf@uniton.integrable-solutions.net \
--to=gdr@integrable-solutions.net \
--cc=aj@suse.de \
--cc=gcc@gcc.gnu.org \
--cc=giovannibajo@libero.it \
--cc=gp@suse.de \
--cc=jason@redhat.com \
--cc=neroden@twcny.rr.com \
--cc=pcarlini@suse.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).