Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@redhat.com>
Cc: pmuldoon@redhat.com, gdb-patches@sourceware.org
Subject: Re: (Doc ping [for news and manual]) --  [PATCH 14/14] the "compile" command
Date: Fri, 20 Jun 2014 19:00:00 -0000	[thread overview]
Message-ID: <83ha3fque7.fsf@gnu.org> (raw)
In-Reply-To: <871tujabhh.fsf@fleche.redhat.com>

> From: Tom Tromey <tromey@redhat.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
> Date: Fri, 20 Jun 2014 08:42:34 -0600
> 
> Eli> That's not what I meant.  Suppose I have 2 compilers installed, one
> Eli> called 'gcc', the other 'gcc472'.  (They could also be in different
> Eli> directories, even not on PATH.)  The program I'm debugging was
> Eli> compiled with gcc472.  How will GDB know to invoke that executable?
> Eli> Also, how would it know the command-line arguments required to produce
> Eli> a code that will work well with the rest of the program being debugged
> Eli> (the code I compile can call functions in the program, right?)?
> 
> Phil> Tom could maybe answer this better.  There was recent work on the GCC
> Phil> triplet and PATH searching over on GCC for the plugin.
> 
> Yes, the new version searches the path for something matching the
> correct GNU configury triplet.

But the triplet is not enough, I could have more than one compiler
installed for the same triplet.

Besides, can we reliably assume that there's a compiler whose name
matches the triplet?  On my MinGW installation of GCC, I don't have
i686-pc-minwg32-gcc anywhere.

> See the gcc patch series for details.

I'd appreciate a URL (assuming this is somewhere in GCC mailing
lists).

Thanks.


  reply	other threads:[~2014-06-20 19:00 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-16 15:26 [PATCH 00/14] let gdb reuse gcc's C compiler Tom Tromey
2014-05-16 15:26 ` [PATCH 08/14] introduce call_function_by_hand_dummy Tom Tromey
2014-05-16 15:26 ` [PATCH 07/14] add infcall_mmap and gcc_target_options gdbarch methods Tom Tromey
2014-05-19  6:13   ` Yao Qi
2014-05-19  6:41     ` Jan Kratochvil
2014-05-19  6:47       ` Jan Kratochvil
2014-05-19  7:42       ` Yao Qi
2014-05-19  8:26         ` Agovic, Sanimir
2014-05-19 11:15           ` Jan Kratochvil
2014-05-16 15:26 ` [PATCH 01/14] introduce ui_file_write_for_put Tom Tromey
2014-05-16 15:26 ` [PATCH 02/14] add gcc/gdb interface files Tom Tromey
2014-05-19  8:06   ` Yao Qi
2014-05-19 13:53     ` Tom Tromey
2014-05-16 15:26 ` [PATCH 10/14] make dwarf_expr_frame_base_1 public Tom Tromey
2014-05-16 15:26 ` [PATCH 03/14] add some missing ops to DWARF assembler Tom Tromey
2014-05-16 15:27 ` [PATCH 14/14] the "compile" command Tom Tromey
2014-06-16  9:55   ` (Doc ping [for news and manual]) -- " Phil Muldoon
2014-06-16 15:25     ` Eli Zaretskii
2014-06-20  9:17       ` Phil Muldoon
2014-06-20  9:42         ` Eli Zaretskii
2014-06-20 10:01           ` Phil Muldoon
2014-06-20 12:37             ` Eli Zaretskii
2014-06-20 14:42             ` Tom Tromey
2014-06-20 19:00               ` Eli Zaretskii [this message]
2014-06-21  7:32                 ` Eli Zaretskii
2014-05-16 15:41 ` [PATCH 05/14] change how the CLI handles comments Tom Tromey
2014-05-18 23:26   ` Doug Evans
2014-05-19 14:07     ` Phil Muldoon
2014-06-03  7:04       ` Doug Evans
2014-05-16 15:43 ` [PATCH 13/14] add s390_gcc_target_options Tom Tromey
2014-05-16 15:43 ` [PATCH 09/14] split dwarf2_fetch_cfa_info from dwarf2_compile_expr_to_ax Tom Tromey
2014-05-16 15:43 ` [PATCH 12/14] add linux_infcall_mmap Tom Tromey
2014-05-16 15:56 ` [PATCH 04/14] add make_unqualified_type Tom Tromey
2014-05-16 16:18 ` [PATCH 11/14] export dwarf2_reg_to_regnum_or_error Tom Tromey
2014-05-16 16:18 ` [PATCH 06/14] add dummy frame destructor 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=83ha3fque7.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pmuldoon@redhat.com \
    --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