Displaying 3 results from an estimated 3 matches for "fnofreestand".
2016 Sep 16
2
RFC: module flag for hosted mode
...nizer has already been run over these modules at compile time, so even if all modules are old there's unlikely to be a huge perf regression.
>
> As an alternative view: since we didn’t support -ffreestanding in LTO mode before, we should be able to just auto-upgrade these bitcode to the -fnofreestanding version.
>
> That said, as you mentioned it is probably not the common case and I don’t expect us to hit this in practice.
I completely agree with Mehdi here. We could auto-upgrade to -fno-freestanding, but it's also not important.
2016 Sep 16
2
RFC: module flag for hosted mode
In PR30403 we've been discussing how to encode -ffreestanding when using
LTO. This bit is currently dropped during LTO because its only
representation is in the TargetLibraryInfo created by clang (
http://llvm-cs.pcc.me.uk/tools/clang/lib/CodeGen/BackendUtil.cpp#258).
The proposal is to introduce a module flag that we set in any translation
unit compiled in hosted (i.e. -fno-freestanding)
2016 Sep 21
2
RFC: module flag for hosted mode
...ile time,
>> so even if all modules are old there's unlikely to be a huge perf
>> regression.
>> >
>> > As an alternative view: since we didn’t support -ffreestanding in LTO
>> mode before, we should be able to just auto-upgrade these bitcode to the
>> -fnofreestanding version.
>> >
>> > That said, as you mentioned it is probably not the common case and I
>> don’t expect us to hit this in practice.
>>
>> I completely agree with Mehdi here. We could auto-upgrade to
>> -fno-freestanding, but it's also not important....