From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: tromey@redhat.com, gdb-patches@sourceware.org
Subject: Re: [PATCH v2 14/14] the "compile" command
Date: Wed, 08 Oct 2014 19:42:00 -0000 [thread overview]
Message-ID: <20141008194233.GA22378@host2.jankratochvil.net> (raw)
In-Reply-To: <83wq8aies9.fsf@gnu.org>
On Wed, 08 Oct 2014 20:42:46 +0200, Eli Zaretskii wrote:
> AFAIK, MinGW compilers simply ignore -fPIC.
My concern was only if the compiler refuses to run with such option which it
does not. I agree it prints:
<stdin>:1:0: warning: -fPIC ignored for target (all code is position independent) [enabled by default]
Before tuning the options to prevent for such target warnings it would be
better to know whether it works at all. Besides other reasons (such as not
having such platform available) I am not interested in this target so I hope
it is OK to leave it up to mingw maintainers to at least test it before
deciding what next.
> But if the feature will only work with these options and no others,
> then I guess it's OK to have them as fixed strings.
As I said these options are required for {i686,x86_64}-linux.
Thanks,
Jan
next prev parent reply other threads:[~2014-10-08 19:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 15:58 [PATCH v2 00/15] let gdb reuse gcc's C compiler Tom Tromey
2014-06-20 15:58 ` [PATCH v2 14/14] the "compile" command Tom Tromey
2014-06-20 19:17 ` Eli Zaretskii
2014-10-08 17:45 ` Jan Kratochvil
2014-10-08 18:42 ` Eli Zaretskii
2014-10-08 19:42 ` Jan Kratochvil [this message]
2014-06-20 15:58 ` [PATCH v2 11/14] export dwarf2_reg_to_regnum_or_error Tom Tromey
2014-06-20 15:58 ` [PATCH v2 09/14] split dwarf2_fetch_cfa_info from dwarf2_compile_expr_to_ax Tom Tromey
2014-06-20 15:58 ` [PATCH v2 04/14] add make_unqualified_type Tom Tromey
2014-06-20 15:58 ` [PATCH v2 02/14] add gcc/gdb interface files Tom Tromey
2014-06-20 15:58 ` [PATCH v2 01/14] introduce ui_file_write_for_put Tom Tromey
2014-06-20 15:58 ` [PATCH v2 03/14] add some missing ops to DWARF assembler Tom Tromey
2014-06-20 16:26 ` [PATCH v2 13/14] add s390_gcc_target_options Tom Tromey
2014-06-20 16:32 ` [PATCH v2 05/14] add dummy frame destructor Tom Tromey
2014-06-20 16:32 ` [PATCH v2 07/14] add gnu_triplet_regexp gdbarch method Tom Tromey
2014-06-20 16:32 ` [PATCH v2 12/14] add linux_infcall_mmap Tom Tromey
2014-06-20 16:33 ` [PATCH v2 10/14] make dwarf_expr_frame_base_1 public Tom Tromey
2014-06-20 20:05 ` Doug Evans
2014-06-23 8:18 ` Gary Benson
2014-06-23 14:57 ` Eli Zaretskii
2014-06-24 10:18 ` Gary Benson
2014-06-24 13:04 ` Pedro Alves
2014-10-08 16:57 ` Jan Kratochvil
2014-06-20 16:39 ` [PATCH v2 08/14] introduce call_function_by_hand_dummy Tom Tromey
2014-06-20 16:51 ` [PATCH v2 06/14] add infcall_mmap and gcc_target_options gdbarch methods Tom Tromey
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=20141008194233.GA22378@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.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).