public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Dara Hazeghi <dhazeghi@yahoo.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: RE: target/6884: [v850] GCC overwrites return address
Date: Tue, 13 May 2003 17:56:00 -0000	[thread overview]
Message-ID: <20030513175602.21863.qmail@sources.redhat.com> (raw)

The following reply was made to PR target/6884; it has been noted by GNATS.

From: Dara Hazeghi <dhazeghi@yahoo.com>
To: Turkia Veikko <Veikko.Turkia@enermet.fi>
Cc: gcc-gnats@gcc.gnu.org
Subject: RE: target/6884: [v850] GCC overwrites return address
Date: Tue, 13 May 2003 10:51:12 -0700 (PDT)

 --- Turkia Veikko <Veikko.Turkia@enermet.fi> wrote:
 > 
 > 
 > > -----Original Message-----
 > > From:	Dara Hazeghi [SMTP:dhazeghi@yahoo.com]
 > > Sent:	Tuesday, May 13, 2003 11:19 AM
 > > To:	Turkia Veikko
 > > Cc:	gcc-gnats@gcc.gnu.org
 > > Subject:	RE: target/6884: [v850] GCC overwrites
 > return address
 > > 
 > > 
 > > --- Turkia Veikko <Veikko.Turkia@enermet.fi>
 > wrote:
 > > > Hello
 > > > 
 > > > Thank you for the reply.
 > > > The project where we have used the gcc has
 > finished
 > > > and now I haven't
 > > > possibility to test this with newer version, but
 > in
 > > > the future I will tell
 > > > you the result.
 > > > The gcc compiles effective binary and these kind
 > > > bugs can be avoid, so it is
 > > > useful compiler.
 > > 
 > > Since you won't be able to check if this bug still
 > > exists, should we perhaps close it, and you can
 > open a
 > > new one, if you should encounter this problem in
 > the
 > > future? Thanks,
 > > 
 > > Dara
 > > 
 > 	[Turkia Veikko]  
 > 	Yes,
 > 	I think you can close this bug and if it exist in
 > the newer versions
 > I will pick it up.
 
 We'll close this one then. Thanks,
 
 Dara
 > 
 > 	t: VT 
 > 
 > 	PS
 > 	This bug doesn't exist at PC environment - so it
 > might be problem of
 > optimizer for NEC V850,
 > 	but if it is still there I'll tell you.
 
 __________________________________
 Do you Yahoo!?
 The New Yahoo! Search - Faster. Easier. Bingo.
 http://search.yahoo.com


             reply	other threads:[~2003-05-13 17:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-13 17:56 Dara Hazeghi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-13  8:26 Dara Hazeghi
2003-05-12 10:39 steven
2003-05-10 23:36 Dara Hazeghi

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=20030513175602.21863.qmail@sources.redhat.com \
    --to=dhazeghi@yahoo.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /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).