Gunther Nikl wrote :
> On Tue, Jan 17, 2006 at 01:35:59PM +0100, Philippe De Muyter wrote:
> > Where is that AmigaOS port availaible ?
> > That seems to be an easier solution.
>
> GCC diffs upto 3.4.0 are available here:
>
>ftp://ftp.back2roots.org/pub/geekgadge
Andreas Schwab wrote :
> "Philippe De Muyter" <[EMAIL PROTECTED]> writes:
>
> > * config/m68k/m68k.md (*addsi3_5200): Allow addq/subq to memory
> > operands.
>
> This is ok, but please send the patch to [EMAIL PROTECTED]
>
> Andreas.
It i
Gunther Nikl wrote :
> On Sat, Jan 14, 2006 at 02:21:20AM +0100, Philippe De Muyter wrote:
> > For an embedded mmu-less m68k target, I would like to generate code
> > that will always run at a fixed place in memory, thus not needing to be PIC,
> > but that would access a
lippe De Muyter <[EMAIL PROTECTED]>
* config/m68k/m68k.md (*addsi3_5200): Allow addq/subq to memory
operands.
--- config/m68k/m68k.md 2005-08-25 10:59:51.0 +0200
+++ config/m68k/m68k.md 2005-08-26 11:24:33.0 +0200
@@ -1861,7 +1887,7 @@
(define_insn &q
For a mmu-less embedded target, I would like to generate code to run at
a fixed location in read-only memory, but with the data segment located
anywhere in memory. Therefore, the accesses to the data segement must go
through an indirection table (GOT).
I do not think that the option exists for my
Hello,
For an embedded mmu-less m68k target, I would like to generate code
that will always run at a fixed place in memory, thus not needing to be PIC,
but that would access a data+bss segment that could be anywhere in memory,
thus needing accesses to the data segment via %a5 and an offset table.
