From: "Leif Ekblad" <leif@rdos.net>
To: "Richard Biener" <rguenther@suse.de>, "Uros Bizjak" <ubizjak@gmail.com>
Cc: <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 06:51:00 -0000 [thread overview]
Message-ID: <E5B069B6BCFF497584F8635FA9BBF98A@AMDP6> (raw)
In-Reply-To: <alpine.LNX.2.00.1301090936130.6889@zhemvz.fhfr.qr>
If the patch is ok, could some maintainer add it to trunk?
Regards,
Leif Ekblad
----- Original Message -----
From: "Richard Biener" <rguenther@suse.de>
To: "Uros Bizjak" <ubizjak@gmail.com>
Cc: "Leif Ekblad" <leif@rdos.net>; <gcc-patches@gcc.gnu.org>; "H.J. Lu"
<hjl.tools@gmail.com>; "Jakub Jelinek" <jakub@redhat.com>
Sent: Wednesday, January 09, 2013 9:37 AM
Subject: Re: [PATCH] Adding target rdos to GCC
> On Wed, 9 Jan 2013, Uros Bizjak wrote:
>
>> On Tue, Jan 8, 2013 at 9:32 PM, Leif Ekblad <leif@rdos.net> wrote:
>> > After some new suggestions from Uros, I've made a new diff.
>> >
>> >
>> > Change log:
>> > * config/gthr.m4: Added rdos thread header.
>> > * gcc/config/i386/i386.c: Provided a way to define a default setting
>> > for
>> > medium memory model and PIC using TARGET_RDOS define.
>> > * gcc/config/i386/i386.h: Defined TARGET_RDOS macro. Defined default
>> > value
>> > for large-data-threshold.
>> > * gcc/config/i386/i386.md: Added r14 and r15 register names.
>> > * gcc/config/i386/i386.opt: Changed initial value for
>> > large-data-threshold
>> > to DEFAULT_LARGE_SECTION_THRESHOLD.
>> > * gcc/config/i386/rdos.h: Common definitions for target rdos
>> > * gcc/config/i386/rdos64.h: Specific definitions for 64-bit rdos
>> > target.
>> > * gcc/config.gcc: Added rdos targets
>>
>> Please use present tense in ChangeLog (see many other entries).
>>
>> > Tested on target rdos and rdos32.
>>
>> This is OK for mainline, but the patch needs explicit approval from
>> Release Managers at this stage.
>
> Ok with me.
>
> Richard.
next prev parent reply other threads:[~2013-01-28 6:51 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 [this message]
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
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=E5B069B6BCFF497584F8635FA9BBF98A@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).