From: Jeff Law <law@redhat.com>
To: Ilya Enkovich <enkovich.gnu@gmail.com>,
Joseph Myers <joseph@codesourcery.com>
Cc: Sandra Loosemore <sandra@codesourcery.com>,
Richard Biener <rguenther@suse.de>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, libmpx, i386, PR driver/65444] Pass '-z bndplt' when building dynamic objects with MPX
Date: Thu, 25 Jun 2015 19:00:00 -0000 [thread overview]
Message-ID: <558C4DE5.20400@redhat.com> (raw)
In-Reply-To: <20150605140102.GA16897@msticlxl57.ims.intel.com>
On 06/05/2015 08:01 AM, Ilya Enkovich wrote:
> On 04 Jun 15:53, Joseph Myers wrote:
>> On Thu, 4 Jun 2015, Ilya Enkovich wrote:
>>
>>> 2015-06-03 18:59 GMT+03:00 Joseph Myers <joseph@codesourcery.com>:
>>>> You could, for example, have
>>>>
>>>> #if SOMETHING
>>>> #define MSG "%nsome msg"
>>>> #else
>>>> #define MSG ""
>>>> #endif
>>>>
>>>> and have another spec using MSG - that should work.
>>>
>>> In this case I should define SOMETHING in configure of gcc, not in
>>> configure of libmpx, right? But it would mean I check host linker, not
>>> target.
>>
>> gcc/ configure tests on the linker generally test the build-x-target
>> linker, which is required to have the same version and be configured the
>> same as the host-x-target linker. (The tests mustn't actually try to link
>> anything, but they can e.g. see if a particular option is mentioned in
>> --help output. In general they also have version number checks for the
>> case of an in-tree linker build.)
>>
>> --
>> Joseph S. Myers
>> joseph@codesourcery.com
>
> Thanks for help! Here is a new patch version with a check moved into gcc/configure. Does it look OK?
>
> Thanks,
> Ilya
> --
> gcc/
>
> 2015-06-05 Ilya Enkovich <enkovich.gnu@gmail.com>
>
> * config/i386/linux-common.h (LINK_MPX): New.
> (MPX_SPEC): Use LINK_MPX instead of %(link_mpx).
> * configure.ac: Add HAVE_LD_BNDPLT_SUPPORT macro
> indicating '-z bndplt' support by linker.
> * configure: Regenerate.
> * config.in: Regenerate.
>
> libmpx/
>
> 2015-06-05 Ilya Enkovich <enkovich.gnu@gmail.com>
>
> * configure.ac: Remove link_mpx.
> * libmpx.spec.in: Likewise.
> * configure: Regenerate.
OK. Sorry for the long wait.
jeff
next prev parent reply other threads:[~2015-06-25 18:52 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 11:56 Ilya Enkovich
2015-03-18 12:03 ` H.J. Lu
2015-03-18 12:05 ` Ilya Enkovich
2015-03-18 12:08 ` H.J. Lu
2015-03-18 12:13 ` Ilya Enkovich
2015-03-18 12:25 ` H.J. Lu
2015-03-18 12:42 ` Richard Biener
2015-03-18 13:24 ` Ilya Enkovich
2015-03-18 13:32 ` H.J. Lu
2015-03-18 13:41 ` Ilya Enkovich
2015-03-18 13:52 ` H.J. Lu
2015-03-18 13:59 ` Ilya Enkovich
2015-03-18 14:02 ` Jakub Jelinek
2015-03-18 14:31 ` H.J. Lu
2015-03-18 14:42 ` H.J. Lu
2015-03-18 16:14 ` Ilya Enkovich
2015-03-18 16:45 ` H.J. Lu
2015-03-18 17:13 ` Ilya Enkovich
2015-03-18 17:14 ` H.J. Lu
2015-03-18 17:34 ` Ilya Enkovich
2015-03-18 17:39 ` H.J. Lu
2015-03-18 18:13 ` Ilya Enkovich
2015-03-18 14:03 ` Robert Dewar
2015-03-18 14:33 ` Markus Trippelsdorf
2015-03-23 10:19 ` Ilya Enkovich
2015-03-31 9:47 ` Ilya Enkovich
2015-04-02 4:34 ` Jeff Law
2015-04-02 11:01 ` H.J. Lu
2015-04-03 19:34 ` Joseph Myers
2015-04-06 1:45 ` Sandra Loosemore
2015-04-06 2:35 ` H.J. Lu
2015-04-06 3:08 ` Sandra Loosemore
2015-04-06 15:18 ` Ilya Enkovich
2015-04-06 15:28 ` Jeff Law
2015-04-06 15:54 ` Ilya Enkovich
2015-05-26 9:26 ` Ilya Enkovich
2015-05-27 15:35 ` Jeff Law
2015-06-03 9:04 ` Ilya Enkovich
2015-06-03 15:29 ` Joseph Myers
2015-06-03 15:59 ` Ilya Enkovich
2015-06-03 16:03 ` Joseph Myers
2015-06-04 14:14 ` Ilya Enkovich
2015-06-04 15:55 ` Joseph Myers
2015-06-05 14:44 ` Ilya Enkovich
2015-06-25 19:00 ` Jeff Law [this message]
2015-04-06 17:15 ` Sandra Loosemore
2015-04-07 19:01 ` Jeff Law
2015-04-07 19:29 ` H.J. Lu
2015-04-07 20:12 ` Markus Trippelsdorf
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=558C4DE5.20400@redhat.com \
--to=law@redhat.com \
--cc=enkovich.gnu@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=rguenther@suse.de \
--cc=sandra@codesourcery.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).