From: Richard Earnshaw <rearnsha@arm.com>
To: Joey Ye <joey.ye@arm.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [patch] [arm] New option for PIC offset unfixed
Date: Thu, 14 Nov 2013 10:48:00 -0000 [thread overview]
Message-ID: <52849F21.6030403@arm.com> (raw)
In-Reply-To: <000001cee112$c9f683c0$5de38b40$@arm.com>
On 14/11/13 08:23, Joey Ye wrote:
>> -----Original Message-----
>> From: Richard Earnshaw
>> Sent: Thursday, November 14, 2013 0:57
>> To: Joey Ye
>> Cc: gcc-patches@gcc.gnu.org
>> Subject: Re: [patch] [arm] New option for PIC offset unfixed
>>
>>> So you are suggesting change like this:
>>> + Target Report Var(arm_pic_data_is_text_relative) Init(-1)
>>>
>>> + if (arm_pic_data_is_text_relative < 0 && TARGET_VXWORKS_RTP)
>>> + arm_pic_data_is_text_relative = 0;
>>> + else
>>> + arm_pic_data_is_text_relative = 1;
>>>
>>
>> No, use the global_options_set structure to find out if the user has set
> the
>> value.
> Thank pointing this out. Here is the latest patch with global_options_set
>
>
This is OK.
However, don't you also need to fix the other references to
TARGET_VXWORKS_RTP; eg pic_offset_arm in arm.md?
R.
next prev parent reply other threads:[~2013-11-14 10:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 10:09 Joey Ye
2013-11-14 10:48 ` Richard Earnshaw [this message]
2013-11-14 12:53 ` Joey Ye
-- strict thread matches above, loose matches on Subject: below --
2013-11-12 10:12 Joey Ye
2013-11-12 13:37 ` Richard Earnshaw
2013-11-13 9:06 ` Joey Ye
2013-11-13 10:52 ` Richard Earnshaw
2013-11-13 11:16 ` Joey Ye
2013-11-13 11:46 ` Richard Earnshaw
2013-11-13 17:23 ` Joey Ye
2013-11-13 12:21 ` Richard Earnshaw
[not found] ` <45520D6299C11E4588128526465332BB3BDBAD147A@SAROVARA.Asiapac.Arm.com>
2013-11-13 18:00 ` Richard Earnshaw
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=52849F21.6030403@arm.com \
--to=rearnsha@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joey.ye@arm.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).