public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Leif Ekblad" <leif@rdos.net>
To: "Uros Bizjak" <ubizjak@gmail.com>
Cc: "Richard Biener" <rguenther@suse.de>,	<gcc-patches@gcc.gnu.org>,
	"H.J. Lu" <hjl.tools@gmail.com>,
	"Jakub Jelinek" <jakub@redhat.com>
Subject: Re: [PATCH] Adding target rdos to GCC
Date: Mon, 28 Jan 2013 20:14:00 -0000	[thread overview]
Message-ID: <123C318BEB9645F6A2E41B86E3648CED@AMDP6> (raw)
In-Reply-To: <CAFULd4b5V-Y9me9yV7bOddjLJAkT=9JZmFO---irZ+7XAUHgUg@mail.gmail.com>


----- Original Message ----- 
From: "Uros Bizjak" <ubizjak@gmail.com>
To: "Leif Ekblad" <leif@rdos.net>
Cc: "Richard Biener" <rguenther@suse.de>; <gcc-patches@gcc.gnu.org>; "H.J. 
Lu" <hjl.tools@gmail.com>; "Jakub Jelinek" <jakub@redhat.com>
Sent: Monday, January 28, 2013 9:03 PM
Subject: Re: [PATCH] Adding target rdos to GCC


> On Mon, Jan 28, 2013 at 8:57 PM, Leif Ekblad <leif@rdos.net> wrote:
>
>> That is intentional. The gthr-rdos.h file is part of libgcc. My intention
>> was to first patch gcc, then update the patches for newlib, and finally
>> libgcc. The gthr-rdos.h file would reference include-files part of 
>> newlib,
>> so this is kind of circular. I also cannot define the thread model for 
>> RDOS
>> unless I define this file.
>>
>> I see a couple of possible solutions:
>> 1. Keep as is. You cannot build libgcc at the current stage anyway, and 
>> the
>> bootstrap must be built without threading
>> 2. Add an empty gthr-rdos.h file until libgcc is done
>> 3. Remove the threading-model for now, and add it with libgcc instead.
>
> I propose option 3.
>
> Is it enough to remove gthr.m4 change from the patch in this case?
>
> Uros.

Yes, for all practical purposes. There is a reference to thread-file in 
config.gcc, when threading is enabled, which doesn't work for bootstrapping 
the compiler anyway.

Regards,
Leif Ekblad

  reply	other threads:[~2013-01-28 20:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-06 20:32 Uros Bizjak
2013-01-07 22:13 ` Leif Ekblad
2013-01-08 20:32   ` Leif Ekblad
2013-01-09  6:58     ` Uros Bizjak
2013-01-09  8:38       ` Richard Biener
2013-01-28  6:51         ` Leif Ekblad
2013-01-28  7:23           ` Uros Bizjak
2013-01-28 19:58             ` Leif Ekblad
2013-01-28 20:03               ` Uros Bizjak
2013-01-28 20:14                 ` Leif Ekblad [this message]
2013-01-28 20:45                   ` Uros Bizjak
2013-01-28 21:44                     ` Leif Ekblad
2013-05-13 19:03                     ` Using GS for TLS on x86-64 for target RDOS Leif Ekblad
  -- strict thread matches above, loose matches on Subject: below --
2013-01-04 22:21 [PATCH] Adding target rdos to GCC Leif Ekblad
2013-01-04 22:32 ` H.J. Lu
2013-01-06 17:08   ` Leif Ekblad

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=123C318BEB9645F6A2E41B86E3648CED@AMDP6 \
    --to=leif@rdos.net \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hjl.tools@gmail.com \
    --cc=jakub@redhat.com \
    --cc=rguenther@suse.de \
    --cc=ubizjak@gmail.com \
    /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).