Displaying 20 results from an estimated 2000 matches similar to: "Where does LTO remove unused functions?"
2020 Jan 28
2
Where does LTO remove unused functions?
Thanks!
On Mon, Jan 27, 2020 at 6:05 PM Teresa Johnson <tejohnson at google.com> wrote:
> By default even regular LTO now has module summaries (like the kind used
> for ThinLTO). LTO will then run index based dead symbol analysis here:
> http://llvm-cs.pcc.me.uk/lib/LTO/LTO.cpp#923. Then when linkRegularLTO is
> called here: http://llvm-cs.pcc.me.uk/lib/LTO/LTO.cpp#935, it
2011 Nov 02
0
[LLVMdev] weak_odr constant versus weak_odr global
Hi
[Adding cfe-dev to widen the net]
On Tue, November 1, 2011 23:19, Richard Smith wrote:
> We recently narrowed down a clang regression to the following testcase:
>
> struct S { static const int x; };
> template<typename T> struct U { static const int k; };
> template<typename T> const int U<T>::k = T::x;
>
> #ifdef TU1
> extern int f();
> const int
2011 Nov 01
6
[LLVMdev] weak_odr constant versus weak_odr global
Hi,
We recently narrowed down a clang regression to the following testcase:
struct S {
static const int x;
};
template<typename T> struct U {
static const int k;
};
template<typename T> const int U<T>::k = T::x;
#ifdef TU1
extern int f();
const int S::x = 42;
int main() {
return f() + U<S>::k;
}
#endif
#ifdef TU2
int f() { return U<S>::k; }
#endif
/* Steps
2011 Nov 02
1
[LLVMdev] [cfe-dev] weak_odr constant versus weak_odr global
On Tue, Nov 1, 2011 at 5:19 PM, Richard Smith <richard at metafoo.co.uk> wrote:
> Hi
>
> [Adding cfe-dev to widen the net]
>
> On Tue, November 1, 2011 23:19, Richard Smith wrote:
>> We recently narrowed down a clang regression to the following testcase:
>>
>> struct S { static const int x; };
>> template<typename T> struct U { static const int k;
2014 Sep 05
2
[LLVMdev] [cfe-dev] weak_odr constant versus weak_odr global
> I see. Using two comdats would still cause the same problem for us,
> no? So the solution in the end is to emit:
>
> TU1:
> --------------------------------
> @_ZN1UI1SE1kE = weak_odr constant i32 42, align 4, comdat _ZN1UI1SE1kE
> @_ZGVN1UI1SE1kE = weak_odr global i64 1, comdat _ZN1UI1SE1kE
> --------------------------------
>
> TU2:
>
2011 Nov 21
0
[LLVMdev] [cfe-dev] weak_odr constant versus weak_odr global
> Unfortunately, making the comdat be for the entire function is not
> conformant with the ABI, which says that you either put the variable
> and its guard in different comdats or you put them in a single comdat
> named for the variable. It also doesn't actually help unless we disable
> inlining.
I see. Using two comdats would still cause the same problem for us,
no? So the
2011 Nov 09
3
[LLVMdev] [cfe-dev] weak_odr constant versus weak_odr global
On Nov 9, 2011, at 11:34 AM, Rafael Espíndola wrote:
>>> 1) [Requires ABI change] We emit dynamic initialization code for weak globals
>>> (even in TUs where static initialization is required to be performed), unless
>>> we can prove that every translation unit will use static initialization. We
>>> emit the global plus its guard variable as a single object so
2011 Nov 07
0
[LLVMdev] weak_odr constant versus weak_odr global
I tried a small variation:
struct S {
static const int x;
};
template<typename T> struct U {
static const int k;
};
template<typename T> const int U<T>::k = T::x;
#ifdef TU1
extern int f();
const int S::x = 42;
int main() {
return f() + reinterpret_cast<long>(&U<S>::k);
}
#endif
#ifdef TU2
int f() { return U<S>::k; }
#endif
and it crashes with gcc too
2011 Nov 09
0
[LLVMdev] [cfe-dev] weak_odr constant versus weak_odr global
>> 1) [Requires ABI change] We emit dynamic initialization code for weak globals
>> (even in TUs where static initialization is required to be performed), unless
>> we can prove that every translation unit will use static initialization. We
>> emit the global plus its guard variable as a single object so the linker can't
>> separate them (this is the ABI change).
2011 Nov 07
3
[LLVMdev] weak_odr constant versus weak_odr global
2011/11/7 Rafael Espíndola <rafael.espindola at gmail.com>:
> I tried a small variation:
>
> struct S {
> static const int x;
> };
> template<typename T> struct U {
> static const int k;
> };
> template<typename T> const int U<T>::k = T::x;
>
> #ifdef TU1
> extern int f();
> const int S::x = 42;
> int main() {
> return f() +
2011 Nov 08
2
[LLVMdev] [cfe-dev] weak_odr constant versus weak_odr global
On Nov 7, 2011, at 9:47 AM, Richard Smith wrote:
>> In cases where the C++ standard requires static initialization,
>> introducing a write violates the guarantees of the C++ standard for static
>> initialization. Therefore, I'm not sure the whole "make the constant
>> writable" approach is actually viable.
>
> There is another problem which afflicts
2011 Nov 27
1
[LLVMdev] [cfe-dev] weak_odr constant versus weak_odr global
On Nov 21, 2011, at 9:05 AM, Rafael Espíndola wrote:
>> Unfortunately, making the comdat be for the entire function is not
>> conformant with the ABI, which says that you either put the variable
>> and its guard in different comdats or you put them in a single comdat
>> named for the variable. It also doesn't actually help unless we disable
>> inlining.
>
2011 Nov 07
0
[LLVMdev] weak_odr constant versus weak_odr global
On Mon, November 7, 2011 16:31, Eli Friedman wrote:
> 2011/11/7 Rafael Espíndola <rafael.espindola at gmail.com>:
>> I tried a small variation:
>>
>>
>> struct S { static const int x;
>> };
>> template<typename T> struct U { static const int k;
>> };
>> template<typename T> const int U<T>::k = T::x;
>>
>>
2016 Apr 18
1
[RFC] Lazy-loading of debug info metadata
>
>> On 2016-Apr-15, at 17:12, David Blaikie <dblaikie at gmail.com> wrote:
>>
>>
>>
>> On Fri, Apr 15, 2016 at 4:04 PM, Duncan P. N. Exon Smith <dexonsmith at apple.com> wrote:
>>
>> > On 2016-Apr-15, at 14:53, David Blaikie <dblaikie at gmail.com> wrote:
>> >
>> >
>> >
>> >> On Fri, Apr
2012 Feb 01
1
Reminder: Xen Hackathon hosted by Oracle, March 6-8, Santa Clara, CA, USA
Hi everybody,
just a quick reminder that the Xen Hackathon is in Oracle, March 6-8,
Santa Clara, CA, USA. We have originally planned for about 25 people,
but already we have 14 people signed up. If you are planning to attend
please sign up quickly, such that I get a feeling for the number of
attendees. I can then go back to Oracle and see whether we can
accommodate more people than we
2019 Sep 14
2
[GSoC 2019] Apply the Clang Static Analyzer to LLVM-based projects - final report
Hello,
Le 29/08/2019 à 01:02, Artem Dergachev a écrit :
> Yay thx!
>
> Sylvestre, is there anything i can help you with in order to get the reports page back up?
Sorry, it took me a while to get that back but here is the report of r371718:
https://llvm.org/reports/scan-build/
> I'd also indeed love to spam people with warnings that they introduced, even if in the form of a
2014 Feb 06
2
Re: Can I move the disk image of the guest while it is running?
----- Original Message -----
> From: "Eric Blake" <eblake@redhat.com>
> To: "Andrew Martin" <amartin@xes-inc.com>
> Cc: "Gergely Horváth" <gergely.horvath@inepex.com>, libvirt-users@redhat.com
> Sent: Thursday, February 6, 2014 9:31:29 AM
> Subject: Re: [libvirt-users] Can I move the disk image of the guest while it is running?
>
2014 Feb 05
4
Re: Can I move the disk image of the guest while it is running?
Thank you Eric,
On 2014-02-05 17:23, Eric Blake wrote:
> Yes, live storage migration is possible; although at the moment, qemu is
> lacking a way to restart the operation if it fails midstream, so libvirt
> only allows the operation if you are willing to temporarily make your
> guest transient.
What does this mean? Will I loose anything if - for example - there is
not enough space on
2014 Feb 05
2
Can I move the disk image of the guest while it is running?
Hello guys!
We want to move some guests' disk images to different locations (within
the same machine, locally), but we do not want to turn off the guests.
Can we do that while the guest is running, like live migration?
I did not find any related documentation or posts about it.
Let's say the guest has a disk at /ssd/image.raw
We want to move that to /hdd/image.raw
Is there any way to
2019 Nov 14
4
JMAP: Re: http API for IMAP
Am 14.11.19 um 14:03 schrieb Benny Pedersen via dovecot:
> Thomas G?ttler via dovecot skrev den 2019-11-14 08:55:
>
>> Is there already an open source imap2jmap server?
>
> why do you say imap here ?
>
> https://www.cyrusimap.org/imap/developer/jmap.html
>
> cyrus already have it, we just wait for dovecot :)
I used my favorite search engine (ecosia) and found