Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Joel Soete <soete.joel@tiscali.be>
To: Carlos O'Donell <carlos@baldric.uwo.ca>
Cc: John David Anglin <dave@hiauly1.hia.nrc.ca>,
	James Morrison <ja2morri@csclub.uwaterloo.ca>,
	Grant Grundler <grundler@parisc-linux.org>,
	parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] glibc-2.3.3 & gcc-snapshot (3.5.0) pb
Date: Sat, 14 Feb 2004 19:29:38 +0000	[thread overview]
Message-ID: <402E7722.2080105@tiscali.be> (raw)
In-Reply-To: <20040214182319.GA8542@baldric.uwo.ca>



Carlos O'Donell wrote:
>>>Aggressive inlining, and inlining mistakes might cause the function to 
>>>disapper. Unless you can produce a *small* testcase the gcc team will
>>>not look at the bug. You can't say "glibc doesn't build with gcc-3.5"
>>>... well I guess you can, but nobody will have a clue how to fix the
>>>issue.
>>
>>And he should say *something*.
>>Pointing at the problem is a first step towards fixing it.
>>Don't wait until you have a "small" test case to point out a problem
>>since one might never (have time to) find one.
>>
>>Even though I fix very few bugs these days, I'm grateful for
>>every bug report.
> 
> 
> I was too harsh, sorry for that, you should really submit a bug report
> saying that glibc 2.3.3 doesn't build with gcc-3.5 on hppa-linux. It's
> the truth, and you don't know why. The best you can do is list the 
> steps you used to recreate the problem.
> 
Ok, I will try to report as much detail as I can.

Thanks for all,
	Joel

  reply	other threads:[~2004-02-14 19:29 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-11  9:22 [parisc-linux] glibc-2.3.3 & gcc-snapshot (3.5.0) pb Joel Soete
2004-02-11 15:32 ` Joel Soete
2004-02-11 16:27   ` Carlos O'Donell
2004-02-11 16:50     ` Joel Soete
2004-02-13 14:35     ` Joel Soete
2004-02-13 19:49       ` Carlos O'Donell
2004-02-14  0:17         ` Grant Grundler
2004-02-14 14:52           ` Joel Soete
2004-02-14 18:23           ` Carlos O'Donell
2004-02-14 19:29             ` Joel Soete [this message]
2004-02-16 17:31               ` Joel Soete
2004-02-17 21:10                 ` Carlos O'Donell
2004-02-18 13:16                   ` Joel Soete
2004-02-18 13:36                     ` Elliott Potter
2004-02-18 14:42                       ` Joel Soete
2004-02-18 16:39                       ` Carlos O'Donell
2004-02-18 17:25                         ` Joel Soete
2004-02-18 18:40                           ` Joel Soete
2004-02-21 19:01                         ` [parisc-linux] glibc-2.3.3 & gcc-snapshot (3.5.0) pb: followup Joel Soete
2004-02-22  6:00                           ` Carlos O'Donell
2004-02-22 16:53                             ` John David Anglin
  -- strict thread matches above, loose matches on Subject: below --
2004-02-08  1:47 [parisc-linux] Re: [PATCH] gcc/config/pa/ftpr.c fixes for new TRAMPOLINE_TEMPLATE in Carlos O'Donell
2004-02-09 17:11 ` [parisc-linux] glibc-2.3.3 & gcc-snapshot (3.5.0) pb Joel Soete
2004-02-09 18:40   ` James Morrison
2004-02-09 19:06     ` Joel Soete
2004-02-10 16:46       ` Joel Soete
2004-02-10 19:14         ` Carlos O'Donell

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=402E7722.2080105@tiscali.be \
    --to=soete.joel@tiscali.be \
    --cc=carlos@baldric.uwo.ca \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=grundler@parisc-linux.org \
    --cc=ja2morri@csclub.uwaterloo.ca \
    --cc=parisc-linux@lists.parisc-linux.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