This is the mail archive of the gcc-patches@gcc.gnu.org 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: [LTO][PATCH] Fix long double precision problem


Doug Kwan (éæå) wrote:
> Would that easier and less error prone if we just emit the precision?
> I looked at the i386 and ia64 backend and found float types with
> precisions 32, 64, 80, 82 and 128. I am not sure if there is an easy
> way to do the search in an architecture-indepedent manner?

You could look at how things like type_for_mode/type_for_size (sp?) are
implemented.  I don't think we can easily go by the names of the types,
since the "same type" will have different names in C, Ada, and Fortran
for example.

But, I think we're trying too hard for complex types, right at the
moment.  The bit_offset/bit_size thing is right for ordinary floating
point types and we should be able to handle that easily.  My guess is
that for complex types we could add DW_AT_GNU_real_type that indicates
which base type is in use.

Thanks,

-- 
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713


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