Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Phil Muldoon <pmuldoon@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>,
	       Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2 1/2] compile: set debug compile: Display GCC driver filename
Date: Mon, 27 Apr 2015 21:49:00 -0000	[thread overview]
Message-ID: <553E9FB0.8050005@redhat.com> (raw)
In-Reply-To: <20150427203618.GA20234@host1.jankratochvil.net>

On 27/04/15 21:36, Jan Kratochvil wrote:
> On Mon, 27 Apr 2015 20:53:46 +0200, Pedro Alves wrote:
>> "wrong" is subjective.  This split is a conscious design decision,
>> that has advantages like insulating the debugger from compiler ICEs.
>
> I haven't looked it up now but IIRC that is not a "conscious design decision"
> but just a workaround of buggy GCC which cannot recover/re-run from
> compilation errors in the same instance.  The ICE resistance was only
> a side-effect.
>

It's not buggy. We are pushing GCC in new ways. It's a side effect of
change. GCC was designed, and has only run, AFAIK, in this way with
the recent changes of libcc1. The state of GCC has never needed to be
preserved and/or reset (say with GDB and cleanups) as if it
encountered a problem it just exited. Change is good.

But this is not the GCC list. And we probably should not further
exhaust GDB'ers patience with GCC internals. If a plan is set, then
lets just go with it and see if it works?

Otherwise we can just explore until one works ;)

Cheers

Phil



      reply	other threads:[~2015-04-27 20:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-23 20:34 Jan Kratochvil
2015-04-23 20:34 ` [PATCH v2 2/2] compile: Add 'set compile-gcc' Jan Kratochvil
2015-04-23 21:08   ` [PATCH v3 " Jan Kratochvil
2015-04-27 15:47     ` Pedro Alves
2015-04-27 17:54       ` Jan Kratochvil
2015-04-27 19:55         ` Pedro Alves
2015-04-27 15:31 ` [PATCH v2 1/2] compile: set debug compile: Display GCC driver filename Pedro Alves
2015-04-27 16:48   ` Jan Kratochvil
2015-04-27 17:19     ` Pedro Alves
2015-04-27 17:52       ` Jan Kratochvil
2015-04-27 19:17         ` Pedro Alves
2015-04-27 20:44           ` Jan Kratochvil
2015-04-27 20:50           ` Jan Kratochvil
2015-04-27 21:49             ` Phil Muldoon [this message]

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=553E9FB0.8050005@redhat.com \
    --to=pmuldoon@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=palves@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