On Wed, Sep 25, 2013 at 10:35 PM, David Kuehling <dvdkh...@gmx.de> wrote:
> Hi YunQuiang,
>
>>>>>> "YunQiang" == YunQiang Su <wzss...@gmail.com> writes:
>
>> I am working on port Debian to mips64el platform (mips64elr2 indeed)
>> When working on boost1.54, it has a libboost-context now which is not
>> exist in boost1.49.
>
>> boost-context has some assembly code then mips64(el) is marked as
>> unsupported for now.  Maybe we should port it to mips64(el)
>
> Your email is a little unclear to me.  I guess the boost-context
> inline-assembly problem is unrelated to the compiler error you mention?
yes, they are 2 different problems
>
> Are you referring to source files
>
>   ./boost_1_54_0/libs/context/src/asm/make_mips32_o32_elf_gas.S
>   ./boost_1_54_0/libs/context/src/asm/jump_mips32_o32_elf_gas.S
>
> ?
Yes.
>
> This should be pretty easy to fix.  I could have a look at it, but I'm
> currently swamped with a lot of work, so may take some time (I didn't
> even have time to upgrade my fuloong from squeeze to wheezy yet).
I have not very much sense on assembly.
>
> It would help a lot if you could give me login access to a (very fast :)
> mips debian machine that has all the required toolchain packages for
> mips64 builds installed.
They are in a internal network, which need a vpn access, which is not
controlled by me.
>
>> There is a gcc internal error like
>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=715526
>
> WRT the compiler error, did you try to reproduce the error with the
> latest 4.8 series GCC built from sources provided by
> http://gcc.gnu.org/?  When tracking down architecture related GCC bugs,
> the GCC people may be much more ressourceful (helpful) then the Debian
> people.  In case you can reproduce the bug, just create a new bug with
> the single preprocessed source file that triggers the bug attached (plus
> GCC command line) here:
The gcc-4.8_4.8-10 in Debian is update to about 2 or 3 weeks ago
>
>   http://gcc.gnu.org/bugzilla/
>
> Just my two cents.
>
>> FYI: mips(el) architectures may be removed from Debian for next
>> release
>
> Yes, bad news.  Maybe you should have CCed debian-mips in your email, to
> raise some more awareness?
>
> As long as the mips64 effort becomes usable within the next years, I for
> one won't miss Debian mips(32)el :)
Yes, o32 has many users for now still.
>
> cheers,
>
> David
> --
> GnuPG public key: http://dvdkhlng.users.sourceforge.net/dk2.gpg
> Fingerprint: B63B 6AF2 4EEB F033 46F7  7F1D 935E 6F08 E457 205F



-- 
YunQiang Su

-- 
You received this message because you are subscribed to the Google Groups 
"loongson-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to loongson-dev+unsubscr...@googlegroups.com.
To post to this group, send email to loongson-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/loongson-dev.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to