public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Corrado Giacomini <Corrado.Giacomini@trema.com>
To: sje@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/6856: -O2 options causes Internal compiler error on hpux11.00
Date: Wed, 19 Feb 2003 17:46:00 -0000	[thread overview]
Message-ID: <20030219174601.3881.qmail@sources.redhat.com> (raw)

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

From: Corrado Giacomini <Corrado.Giacomini@trema.com>
To: Steve Ellcey <sje@cup.hp.com>
Cc: ebotcazou@libertysurf.fr, gcc-bugs@gcc.gnu.org, harri.pasanen@trema.com,
        nobody@gcc.gnu.org, sje@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Subject: Re: optimization/6856: -O2 options causes Internal compiler error
 on hpux11.00
Date: Wed, 19 Feb 2003 18:30:03 +0100

 --------------040605020001060803060704
 Content-Type: text/plain; charset=us-ascii; format=flowed
 Content-Transfer-Encoding: 7bit
 
 Hi,
 sorry for the my belated answer..
 we are actually using the patch on our gcc32 installation on HP and it 
 solved our problem.
 I didn't used yet the latest GCC 3.3 so I can't say much about that..
 but if Steve say is working better than will certainly install the new 
 GCC 3.3
 as soon as it will be officialy released.
 
 -Corrado
 
 Steve Ellcey wrote:
 
 >>Great! ;-)
 >>
 >>So what to do with this PR?
 >>
 >>-- 
 >>Eric Botcazou
 >>    
 >>
 >
 >I just tried to reproduce the problem with GCC 3.3 bits and the bug does
 >not appear to happen anymore so I think some other change has fixed the
 >problem.  I would say we can resolve this as "cannot reproduce".
 >
 >Steve Ellcey
 >sje@cup.hp.com
 >
 >  
 >
 
 
 --------------040605020001060803060704
 Content-Type: text/html; charset=us-ascii
 Content-Transfer-Encoding: 7bit
 
 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
 <html>
 <head>
   <title></title>
 </head>
 <body>
 Hi,<br>
 sorry for the my belated answer..<br>
 we are actually using the patch on our gcc32 installation on HP and it solved
 our problem.<br>
 I didn't used yet the latest GCC 3.3 so I can't say much about that..<br>
 but if Steve say is working better than will certainly install the new GCC
 3.3 <br>
 as soon as it will be officialy released.<br>
 <br>
 -Corrado<br>
 <br>
 Steve Ellcey wrote:<br>
 <blockquote type="cite" cite="mid200302191654.IAA20097@hpsje.cup.hp.com">
   <blockquote type="cite">
     <pre wrap="">Great! ;-)
 
 So what to do with this PR?
 
 -- 
 Eric Botcazou
     </pre>
   </blockquote>
   <pre wrap=""><!---->
 I just tried to reproduce the problem with GCC 3.3 bits and the bug does
 not appear to happen anymore so I think some other change has fixed the
 problem.  I would say we can resolve this as "cannot reproduce".
 
 Steve Ellcey
 <a class="moz-txt-link-abbreviated" href="mailto:sje@cup.hp.com">sje@cup.hp.com</a>
 
   </pre>
 </blockquote>
 <br>
 </body>
 </html>
 
 --------------040605020001060803060704--
 


             reply	other threads:[~2003-02-19 17:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-19 17:46 Corrado Giacomini [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-07 10:13 giovannibajo
2003-05-07  8:36 Dara Hazeghi
2003-02-19 16:56 Steve Ellcey
2003-02-19 16:46 Eric Botcazou
2003-02-19 16:36 Steve Ellcey
2003-02-19 10:13 ebotcazou
2002-07-29  9:16 Steve Ellcey
2002-05-29  5:16 corrado.giacomini

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=20030219174601.3881.qmail@sources.redhat.com \
    --to=corrado.giacomini@trema.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=sje@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).