--- Comment #7 from zippel at gcc dot gnu dot org 2008-04-01 17:53 ---
Actually for the PCH issue there is a fix:
http://gcc.gnu.org/ml/gcc-patches/2007-09/msg01607.html
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25343
--- You are receiving this mail because: ---
You
--- Comment #6 from zippel at linux-m68k dot org 2007-01-31 18:20 ---
This bug can be closed, it's really a bug in binutils triggered by some inline
assembly in cln. Here is a bit more info:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=388000
--
http://gcc.gnu.org/bug
Hi,
On Sat, 9 Dec 2006, Matthias Klose wrote:
> Roman, do you intend to provide a fix for gcc-4.1?
Attached, it's an update to the m68k-fpcompare patch.
For the log: Allow any fp constant as any immediate operand during and
after reload, even for special constants in case reload can't find a fr
Hi,
On Thu, 16 Nov 2006, Bill Allombert wrote:
> On Sat, Oct 21, 2006 at 06:19:20AM -0700, Matthias Klose wrote:
> > Source: gcc-4.1
> > Source-Version: 4.1.1ds2-17
> >[Roman Zippel]
> >* debian/patches/m68k-secondary-addr-reload.dpatch: Add secondary reloads
Hi,
I looked at it and it's not really a gcc bug, it's more of a binutils bug,
but cln plays some rather weird games, which finally confuses as, so it's
not completely faultless.
I submitted a patch to cln (#388000) which avoids the problem, so this bug
can be closed.
bye, Roman
--
To UNSUB
Hi,
Here are a few patches, which hopefully get us a big step closer to a
working compiler on m68k. There are only lightly tested (i.e. verified
they fix problem via cross compiler). I'm currently building a reduced
package with it (e.g. java has to wait...) and then I'll see what's left.
The
Hi,
On Sun, 14 Aug 2005, Marco d'Itri wrote:
> Compiling tin 1.7.10+20050727 on m68k fails.
>
> gcc -DHAVE_CONFIG_H -I. -I../include -I/usr/include
> -DLOCALEDIR=\"/usr/share/locale\" -I../include -DUSE_CANLOCK -D_GNU_SOURCE
> -g -O2 -c ./save.c
> ./save.c: In function 'uudecode_line':
> .
Hi,
Joshua Kwan wrote:
> gcc-4.0 ICEs on m68k while trying to build flac 1.1.2-3.
This bug is fixed by this patch:
http://gcc.gnu.org/ml/gcc-patches/2005-07/msg01677.html
Bugs 318292, 322532, 328453, 323016 are basically all caused by this
problem.
bye, Roman
--
To UNSUBSCRIBE, email to [EM
Hi,
Daniel Bonniot wrote:
In my case, I don't really want to debug gcc, but I want to make an
upstream bug report as precise as possible. So including a stack trace
would be a bonus. It should help narrowing the nature of the bug, so
that the appriopriate upstream author can start investigating,
--
What|Removed |Added
CC||zippel at linux-m68k dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10692
--- You are receiving
--- Additional Comments From zippel at linux-m68k dot org 2004-06-06 17:21
---
Here is a bit more info, this is the situation before reload:
(insn 365 364 366 18 bug-187564.i:90 (set (reg:SI 277)
(plus:SI (mult:SI (reg:SI 275)
(const_int 8 [0x8
also in
latest tree, but it seems not to be in 3.0.
I've put a test case at http://www.xs4all.nl/~zippel/sha.i, it's a
precompiled example from coreutils. Here is the important part:
void
sha_process_block (const void *buffer, size_t len, struct sha_ctx *ctx)
{
const md5_uint32
Hi,
On Tue, 2 Apr 2002, Matthias Klose wrote:
> - m68k: the branch doesn't bootstrap. Roman wanted to look at it,
> but I got no feedback.
Sorry, I'm busy lately with other projects and it will likely not get
better in the next weeks, but I'll try to get it at least working again
asap.
bye, R
Hi,
Morten Brix Pedersen wrote:
> int main()
> {
> string test = "IUHASISAHDNI";
>
> vector vec;
> for (int i = 0; i <= 50; ++i) {
> string newstr;
> test += "NAWNASDKJNKNN";
> newstr = test;
String assignments are threadsafe now with gcc-3.0, so that wil
Hi,
Matt Zimmerman wrote:
> [EMAIL PROTECTED]:/unstable/build/mdz/hercules-2.12$ cc -O2 -c test.c
> /tmp/cc23gVSZ.s: Assembler messages:
> /tmp/cc23gVSZ.s:69: Error: operands mismatch -- statement `add.l
> %a4,-20(%a6)' ignored
Attached patch fixes this.
Matthias, the same bug still exists in 3
Hi,
Matthias Klose wrote:
> m68k- status unknown, no build reports upstream (May, June)
I will be very likely that the official release won't work on m68k, but
I can provide patches to get it working.
It's also important to note that it needs the very latest binutils
release (2.11.90.0.15).
16 matches
Mail list logo
