public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Daniel Berlin <dberlin@dberlin.org>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] GNU/Hurd config -pthread/profiling update
Date: Mon, 06 Aug 2007 00:52:00 -0000	[thread overview]
Message-ID: <20070806005206.GN4136@interface.famille.thibault.fr> (raw)
In-Reply-To: <4aca3dc20708051640t6a4a0c02gdf66772df42d6de8@mail.gmail.com>

Daniel Berlin, le Sun 05 Aug 2007 19:40:58 -0400, a écrit :
> You need to say what platform you have bootstrapped and regression
> tested these patches on.

This was tested on GNU/Hurd (debian) only since that's the only platform
that uses these config files.

The pthread part has been tested in debian for a long time and permits
the -pthread option to work.

I've tested the profile part with all of:

gcc
gcc -static
gcc -shared
gcc -p
gcc -pg
gcc -profile
gcc -p -static
gcc -pg -static
gcc -profile -static

And all get the corresponding expected behavior. The -profile option
previously wasn't recognized, and -p/-pg were producing programs that
immediately segfault very early in libc initialization.

Samuel

  reply	other threads:[~2007-08-06  0:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-03 21:00 [PATCH] GNU/Hurd config profiling update Samuel Thibault
2007-08-03 20:26 ` [PATCH] GNU/Hurd config -pthread update Samuel Thibault
2007-08-04 21:19   ` [PATCH] GNU/Hurd config -pthread/profiling update Samuel Thibault
2007-08-05 23:41     ` Daniel Berlin
2007-08-06  0:52       ` Samuel Thibault [this message]
2007-08-06  1:40         ` Daniel Berlin
2007-08-08  0:32   ` [PATCH] GNU/Hurd config -pthread update Ian Lance Taylor
2007-08-08  6:38     ` Matthias Klose
2007-08-05 15:43 ` [PATCH] GNU/Hurd config profiling update Alfred M. Szmidt
2007-08-05 15:57   ` Samuel Thibault
2007-08-05 16:14     ` Alfred M. Szmidt
2007-08-05 16:32       ` Samuel Thibault
2007-08-08  0:33 ` Ian Lance Taylor
2007-08-08  6:38   ` Matthias Klose

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=20070806005206.GN4136@interface.famille.thibault.fr \
    --to=samuel.thibault@ens-lyon.org \
    --cc=dberlin@dberlin.org \
    --cc=gcc-patches@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).