This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Tue, Feb 8, 2011 at 11:05 PM, Titus von Boxberg <titus@v9g.de> wrote: > Am 07.02.2011 um 16:53 schrieb Bryan Hundven: > >> On Mon, Feb 7, 2011 at 7:51 AM, Bryan Hundven <bryanhundven@gmail.com> wrote: >>> On Mon, Feb 7, 2011 at 3:29 AM, David Brown <david@westcontrol.com> wrote: >>>> On 07/02/2011 12:14, Titus von Boxberg wrote: >>>>> >>>>> Am Mo, 7.02.2011, 11:16 schrieb David Brown: >>>>>> >>>>>> On 06/02/2011 12:48, Titus von Boxberg wrote: >>>>>>> >>>>>>> Hi all, >>>>>>> >>>>>>> I'm trying to use ct-ng (of approx. May 2010) to generate >>>>>>> cross gcc-4.5.1, glibc-2.9/linux for a powerpc e500v2 / SPE. >>>>>>> >>>>>>> Setting floating point to "hardware" results in a build >>>>>>> error in glibc where the assembler complains while compiling >>>>>>> an FP file about an unmatched constraint >>>>>>> (I could try to get the original message if it helps). >>>>>>> >>>>>>> The tool chain gets built when I set floating point support to >>>>>>> "software". >>>>>>> However, the resulting compiler does not emit hardware FP instructions >>>>>>> unless I give -mhard-float on the command line. >>>>>>> >>>>>>> Is my assumption correct that setting floating point to "hardware" turns >>>>>>> on >>>>>>> code generation for the standard PowerPC FPU which this target lacks? >>>>>>> >>>>>>> I'd like to avoid having a compiler which needs target specific flags >>>>>>> on the command line, thus: >>>>>>> Does anyone know which options to turn on to get a compiler that >>>>>>> emits correct SPE FP instructions without explicitly being told so >>>>>>> by -mhard-float? >>>>>>> >>>>>>> Regards >>>>>>> Titus >>>>>>> >>>>>> >>> >>> Titus, >>> >>> I use the e500v2 toolchain all the time. Please provide more info >>> about the build problem your having and what distribution/version you >>> are building on. >>> >>> I am also hoping to have an e500mc (32 and 64-bit) toolchain samples soon. > Bryan, Yann, all, > > glibc-2.9 now builds. > The settings required are > - hard fp in ct-ng > - disabling fp in glibc (--without-fp) > - possibly the assembler flag -Wa,e500x2 in CFLAGS > - patching away in a powerpc-makefile the rule to use > ÂCFLAGS+=-msoft-float when given --without-fp to configure Hmm. Something sounds odd here. you want a hard float toolchain, but add -msoft-float? > I did not test the result. > If you are interested in a more detailed description of the steps > I found nessecary, I'd start again from scratch and send you a > protocol of the errors without those steps. > I'd rather concentrate on eglibc because these problems and > (untested) solutions look a bit too weird for me. weird. What is your build host? did you have any changes to ctng before you started seeing these problems? what does your config look like? > Just let me know. > > Regards > Titus > > -Bryan -- For unsubscribe information see http://sourceware.org/lists.html#faq
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |