This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Add Android related compilation options and multilib options

I firstly have tried to mimic the new scheme on SH. But later I found
that on SH, the orginal t-mlib-* files are very simple. Each file just
gives an MULTILIB_OPTIONS value. So it is very easy to unify these
t-mlib-* files.
For arm target, the t-mlib-* files contain not only MULTILIB_OPTIONS
I haven't found an easy way to unify these t-mlib-* files into config.gcc.
I can use CASE statement to group these specifications together. But I
am not sure if this approach is better than individual t-mlib-* files.
SH previously had 24 t-mlib-* files. We only have 3 t-mlib-* files for
arm. So I guess maybe it is ok to leave them this way? If there are
more t-mlib-* needed in the future, we can change the scheme.

If anyone has better idea, I am very happy to take it.

Thanks very much!


On Mon, Jun 15, 2009 at 6:02 PM, Joseph S. Myers<> wrote:
> On Mon, 15 Jun 2009, Jing Yu wrote:
>> ? ? ? ? * config/arm/t-mlib-armv7a: New.
>> ? ? ? ? * config/arm/t-mlib-mandroid: New.
>> ? ? ? ? * config/arm/t-mlib-mthumb-interwork: New.
> SH used to use a lot of t-mlib-* files but no longer does. ?Is there some
> reason the new SH scheme is unsuitable for ARM?
> --
> Joseph S. Myers

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]