public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dave Korn <dave.korn.cygwin@gmail.com>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: Christian Joensson <christian.joensson@gmail.com>,
	 gcc-patches@gcc.gnu.org, Kai Tietz <ktietz@redhat.com>
Subject: Re: Failure to bootstrap trunk with --enable-threads=posix on cygwin since r180767
Date: Tue, 08 Nov 2011 18:39:00 -0000	[thread overview]
Message-ID: <4EB975DE.1050509@gmail.com> (raw)
In-Reply-To: <yddty6etrds.fsf@manam.CeBiTec.Uni-Bielefeld.DE>

On 08/11/2011 18:12, Rainer Orth wrote:
> Dave Korn writes:
> 
>>   Notice how in your additions, you prepend the t-mingw-pthread file to the
>> list in $tmake_file rather than append it as the existing code does.  Ordering
>> of t-* files in $tmake_file is significant as there may be overrides and files
>> should be listed from most generic to most target/os-specific, so please
>> adjust those two hunks to match the way it's already being done.
> 
> Huh?  I've done it exactly the way it had been in gcc/config.gcc before
> my patch series:
> 
>         case ${enable_threads} in
>           "" | yes | win32)       thread_file='win32'
>             tmake_file="${tmake_file} i386/t-gthr-win32"
>             ;;
>           posix)
>             thread_file='posix'
>             tmake_file="i386/t-mingw-pthread ${tmake_file}"
>             ;;
>         esac
> 
> Why should this suddenly be wrong in libgcc?

  Hm.  Well, it must have been inconsistent when it was added there in the
first place, so I guess since it hasn't been a problem yet there's no need to
fix it now.  Patch is OK as-is then.

    cheers,
      DaveK

  reply	other threads:[~2011-11-08 18:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CABxpwDkCOnjzoVmxjDpTe3xZqbcbQq_9k+x6B+KKswfGymSbbA@mail.gmail.com>
2011-11-07 18:54 ` Rainer Orth
2011-11-08 18:18   ` Dave Korn
2011-11-08 18:20     ` Rainer Orth
2011-11-08 18:39       ` Dave Korn [this message]
2011-11-08 18:36   ` Christian Jönsson

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=4EB975DE.1050509@gmail.com \
    --to=dave.korn.cygwin@gmail.com \
    --cc=christian.joensson@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=ktietz@redhat.com \
    --cc=ro@CeBiTec.Uni-Bielefeld.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).