Re: [PATCH 32/35] m68k: add ColdFire FPU support for the V4e ColdFire CPU's

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


Hi Greg,

On Wed, Dec 28, 2011 at 06:53, Greg Ungerer <gerg@xxxxxxxxxxxx> wrote:
If we are compiling specifically for a 68040 machine, where we put
a -m68040 switch on the command line, isn't all these ".chip 68k"
lines going to undo the CPU choice - and result in us now compiling
large parts of the code for the default 68020 instead of the chosen
68040?

No, it's a directive for the assembler, not for the compiler.
It may cause issues for mnemonics (generated by the compiler) that
exist for both classic and coldfire, but have different opcodes.
Do these actually exist?

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Video for Linux]     [Photo]     [Yosemite News]    [Yosemite Photos]    [Video Projectors]     [Linux Kernel]     [Linux SCSI]     [XFree86]

Add to Google Powered by Linux