Re: [patch] m68k extendqidi2 fix
- To: Rafael Laboissiere <rafael@debian.org>, m68k-build@nocrew.org
- Cc: Matthias Klose <doko@cs.tu-berlin.de>, Richard Zidlicky <rz@linux-m68k.org>, debian-gcc@lists.debian.org, jwe@bevo.che.wisc.edu
- Subject: Re: [patch] m68k extendqidi2 fix
- From: "Christian T. Steigies" <cts@debian.org>
- Date: Wed, 2 Mar 2005 19:28:20 +0100
- Message-id: <[🔎] 20050302182820.GA30323@skeeve>
- Mail-followup-to: Rafael Laboissiere <rafael@debian.org>, m68k-build@nocrew.org, Matthias Klose <doko@cs.tu-berlin.de>, Richard Zidlicky <rz@linux-m68k.org>, debian-gcc@lists.debian.org, jwe@bevo.che.wisc.edu
- In-reply-to: <[🔎] 20050302101635.GR28730@laboiss2>
- References: <[🔎] 20050302001607.GA1707@linux-m68k.org> <[🔎] 16933.35486.767485.412438@gargle.gargle.HOWL> <[🔎] 20050302101635.GR28730@laboiss2>
On Wed, Mar 02, 2005 at 11:16:35AM +0100, Rafael Laboissiere wrote:
> * Matthias Klose <doko@cs.tu-berlin.de> [2005-03-02 10:42]:
>
> > I'm applying the patch for 3.4 now, debian-m68k, should the patch
> > applied without testing to 3.3 as well?
>
> I think you should apply the patch, because the build daemons use gcc 3.3
> for building the packages. I can provide an indirect test to the patch in
> the next upload of the octave2.1 package. In the last upload, I changed a
> CFLAG from -O1 to -O0 for m68k and the compilation succeeded (I have no idea
> whether this really contributed to fix the problem). I can restore the old
> flag and we will see what happens.
Now that explains why it suddenly built!
So let's ask the other m68k people if it should be included. Could it break
more than it fixes?
Christian
Reply to: