Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@polymtl.ca>,
	Jan Vrany <jan.vrany@fit.cvut.cz>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix various tests to use -no-pie linker flag when needed
Date: Wed, 17 Oct 2018 15:47:00 -0000	[thread overview]
Message-ID: <4e2d9d5a-5381-faf1-a5ee-425158f07b97@redhat.com> (raw)
In-Reply-To: <01b5605a3df81c4d773a82e8648051fa@polymtl.ca>

On 10/16/2018 11:18 PM, Simon Marchi wrote:
> On 2018-10-14 05:59, Jan Vrany wrote:

>> No, I don't know how universal -no-pie is. From what I have understood
>> from Simon (https://sourceware.org/ml/gdb-patches/2018-08/msg00662.html),
>> out of the options available -no-pie is still the best bet.
> 
> gcc supports it, icc supports it [1], clang supports it starting at version 6 according to my testing.  I think this is universal 
> enough that we can use it.  If somebody stumbles on a compiler that does not understand -no-pie and they really need to use it for 
> their testing, they can quite easily add an option for gdb_compile.  

Not sure it's that universal.  See:

  https://github.com/xd009642/tarpaulin/issues/7#issuecomment-317180523

For example, the gcc 4.8 I have handy (our minimum supported version) does
not support it:

 $ /opt/gcc-4.8/bin/gcc /home/pedro/gdb/tests/main.c -o main -no-pie
 gcc: error: unrecognized command line option ‘-no-pie’

> But for now, I don't think it's worth the extra work.

I disagree.

Thanks,
Pedro Alves


  parent reply	other threads:[~2018-10-17 15:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-28 19:37 Jan Vrany
2018-09-07 20:43 ` Tom Tromey
2018-09-07 22:18   ` Simon Marchi
2018-10-14  9:59     ` Jan Vrany
2018-10-16 22:18       ` Simon Marchi
2018-10-17 13:55         ` Tom Tromey
2018-10-17 14:56           ` [PATCH v2] " Jan Vrany
2018-10-17 15:12             ` [PATCH v3] " Jan Vrany
2018-10-17 15:44               ` Simon Marchi
2018-10-17 15:53                 ` Simon Marchi
2018-10-17 19:33                   ` Jan Vrany
2018-12-13 15:21                   ` [PATCH] " Jan Vrany
2018-12-13 17:13                     ` Simon Marchi
2018-12-21 20:56                       ` Simon Marchi
2018-10-17 15:47         ` Pedro Alves [this message]
2018-10-17 15:51           ` Simon Marchi

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=4e2d9d5a-5381-faf1-a5ee-425158f07b97@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.vrany@fit.cvut.cz \
    --cc=simon.marchi@polymtl.ca \
    --cc=tom@tromey.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