[Xorg-driver-geode] proposal: always build with -march=geode

[Writer, Tim]

I'm top posting for consistency with this thread. What is the list
etiquette regarding top posting?

I'm also curious about list etiquette regarding replying/copying off
list. On most mailing lists, I would reply only to the list but I've
noticed many posters variously replying to other posters and copying the
list or replying to the list and copying posters. Is that because
they're using crappy mail clients that get this wrong or is this
accepted practice for this list?

In reference to the original question about `-march=geode', I'm unclear
on the motivation. Is it to avoid generation of i686 instructions that
are invalid on Geode, to optimize for Geode, or something else.

Martin-Éric, can you explain?

Tim

On Tue, Jun 29 2010, "Huang, FrankR" <FrankR.Huang at amd.com> wrote:

> Tim,
>
>         What's your suggestion for this?
>
> Thanks,
> Frank
>
> -----Original Message-----
> From: xorg-driver-geode-bounces+frankr.huang=amd.com at lists.x.org [mailto:xorg-driver-geode-bounces+frankr.huang=amd.com at lists.x.org] On Behalf Of Martin-éric Racine
> Sent: 2010年6月23日 3:07
> To: Geode Mailing List; Gaetan Nadon
> Subject: [Xorg-driver-geode] proposal: always build with -march=geode
>
> Greetings,
>
> Noticing Gaetan Nadon's proposed patch to prevent the building of
> xf86-video-geode on non-x86 platforms, I was wondering if we should
> take this approach one step further:
>
> In addition to exiting gracefully with a warning at ./configure time
> if the build host is non-x86, what if we enforced -march=geode if GCC
>>= 4.3 is found (or -march=i586 if an older version is found)? In our
> Geode driver's case, not only do we know which platforms to exclude,
> we also know the target platform to always be -march=geode. In order
> to accommodate the default compiler flags of distributions, we could
> make the setting of our -march flags only be used if the -march option
> is not already set.
>
> Alternately, we could make ./configure also accept Atom and x86_64 as
> suitable build hosts, in which case we'd have to enforce -march=geode
> always.
>
> Comments?
> --
> Martin-Éric
> _______________________________________________
> Xorg-driver-geode mailing list
> Xorg-driver-geode at lists.x.org
> http://lists.x.org/mailman/listinfo/xorg-driver-geode