Hi Luis,
On 05/17/2012 12:58 PM, Luis Alves wrote:
I've built a new toolchain using the latest tools and gcc-4.6.4
(gcc-4.7.0 is giving me compiler internal errors!).
But unfortunately the results are the same (bad assembly code - It
look it is producing 68020 code, since when I use the -m68020
Hi Greg,
Yes, that file exists in the sources gcc-version/gcc/config/m68k/uclinux.h
I've changed those flags and it works (at least in a small test with
the first pass gcc).
But take a look at the comments in my bug report:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53386
Someone says that it
On Thu, May 17, 2012 at 03:21:12PM +0100, Luis Alves wrote:
Hi Greg,
Yes, that file exists in the sources gcc-version/gcc/config/m68k/uclinux.h
I've changed those flags and it works (at least in a small test with
the first pass gcc).
But take a look at the comments in my bug report:
With a little cleanup we can use much of the entry.S code on both the
MMU and non-MMU m68k targets.
This is the second iteration of this patch set. I have limited the
changes converting to use the ret_from_exception function entry point
over the label. I have only changed those shared by both
From: Greg Ungerer g...@uclinux.org
The ret_from_excption code is referenced by its function name, or by a label
set at the start of its code. The non-MMU code can share some of this code
if we make direct calls to ret_from_exception instead of the associated label.
The effected function paths
From: Greg Ungerer g...@uclinux.org
There is a few places that the m68k entry code uses the bsrl instruction
to call other functions. That instruction is only supported on 68020 and
higher CPU types. If we use jbsr instead the code will be clean for all
68k and ColdFire CPU types.
Signed-off-by:
From: Greg Ungerer g...@uclinux.org
Some of the entry.S code is common to both MMU and non-MMU builds.
So merge the entry_no.S and entry_mm.S files back into a single file.
With a little code movement we only need a single #ifdef.
Signed-off-by: Greg Ungerer g...@uclinux.org
---
Hi Luis,
On 18/05/12 00:21, Luis Alves wrote:
Yes, that file exists in the sources gcc-version/gcc/config/m68k/uclinux.h
I've changed those flags and it works (at least in a small test with
the first pass gcc).
But take a look at the comments in my bug report:
