Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Christophe LYON <christophe.lyon@st.com>
To: Carlos Eduardo Seo <cseo@linux.vnet.ibm.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] testsuite gdb.base/expand-psymtabs: ensure code is generated  for the expected source line
Date: Thu, 11 Dec 2008 08:50:00 -0000	[thread overview]
Message-ID: <4940D41C.4040206@st.com> (raw)
In-Reply-To: <493FFC31.7070005@linux.vnet.ibm.com>

On 10.12.2008 18:28, Carlos Eduardo Seo wrote:
> Christophe LYON wrote:
>> I propose the attached small patch to expand-psymtabs.c. The goal is to
>> make sure the compiler actually generates code and debug information for
>> the expected line. Currently, our compiler attaches code only to the
>> opening brace, hence causing the test to fail.
>>
> 
> Just curious... which compiler are you using?
> 
> gcc generates the right code for the purpose of the test using both
> (patched and unpatched) testcases. So, if everyone else agrees, I'm fine
> with your modification.
> 
> Regards,
> 

We are using Open64. Its front-end is based on GCC but the "trees" are 
converted into Whirl (Open64 Internal Representation) rather early.

We have ported it to internal targets, and on a few occasions, I already 
submitted this kind of small patches.

Christophe.


  reply	other threads:[~2008-12-11  8:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-08 15:25 Christophe LYON
2008-12-10 17:29 ` Carlos Eduardo Seo
2008-12-11  8:50   ` Christophe LYON [this message]
2008-12-15 12:02   ` Christophe LYON
2008-12-16  6:29 ` Joel Brobecker
2008-12-16 10:28   ` Christophe LYON
2008-12-16 13:19     ` Denis PILAT

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=4940D41C.4040206@st.com \
    --to=christophe.lyon@st.com \
    --cc=cseo@linux.vnet.ibm.com \
    --cc=gdb-patches@sources.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