search for: nadlinger

...oão Matos <ripzonetriton at gmail.com>: > I think so. There have been other reports lately related to this being > wrong. > > http://llvm.org/bugs/show_bug.cgi?id=14410 > > CC'ing Timur since he might know more about this. > > On Wed, Feb 20, 2013 at 5:27 PM, David Nadlinger <code at klickverbot.at> > wrote: >> >> On Tue, Feb 19, 2013 at 2:13 PM, Duncan Sands <baldrick at free.fr> wrote: >> >> My question: Is there an easy way of disabling the name-mangling part >> >> but keep the rest of the CC that I missed? >>...

I think so. There have been other reports lately related to this being wrong. http://llvm.org/bugs/show_bug.cgi?id=14410 CC'ing Timur since he might know more about this. On Wed, Feb 20, 2013 at 5:27 PM, David Nadlinger <code at klickverbot.at>wrote: > On Tue, Feb 19, 2013 at 2:13 PM, Duncan Sands <baldrick at free.fr> wrote: > >> My question: Is there an easy way of disabling the name-mangling part > >> but keep the rest of the CC that I missed? > > if you use "\1&quot...

...mail.com>: >> I think so. There have been other reports lately related to this being >> wrong. >> >> http://llvm.org/bugs/show_bug.cgi?id=14410 >> >> CC'ing Timur since he might know more about this. >> >> On Wed, Feb 20, 2013 at 5:27 PM, David Nadlinger <code at klickverbot.at> >> wrote: >>> >>> On Tue, Feb 19, 2013 at 2:13 PM, Duncan Sands <baldrick at free.fr> wrote: >>> >> My question: Is there an easy way of disabling the name-mangling part >>> >> but keep the rest of the CC tha...

On Sun, Oct 6, 2013 at 10:40 PM, Sylvestre Ledru <sylvestre at debian.org> wrote: > I did some cleanup of the repositories today (Sunday). > I remove all the 3.3 snapshots which were wrong (they were older than the > official 3.3 release and not maintained). > I didn't think that anybody was using them (Looks like I was wrong, sorry!). No problem, we were just using them

On Tue, Feb 19, 2013 at 2:13 PM, Duncan Sands <baldrick at free.fr> wrote: >> My question: Is there an easy way of disabling the name-mangling part >> but keep the rest of the CC that I missed? > if you use "\1" + "usual name", it will disable name mangling if you are > lucky. A leading \1 is LLVM's way of saying: leave this name alone! Seems like

...There have been other reports lately related to this being > >> wrong. > >> > >> http://llvm.org/bugs/show_bug.cgi?id=14410 > >> > >> CC'ing Timur since he might know more about this. > >> > >> On Wed, Feb 20, 2013 at 5:27 PM, David Nadlinger <code at klickverbot.at> > >> wrote: > >>> > >>> On Tue, Feb 19, 2013 at 2:13 PM, Duncan Sands <baldrick at free.fr> > wrote: > >>> >> My question: Is there an easy way of disabling the name-mangling > part > >>> >&...

...the packages are maintained by the LLVM project and kept on llvm.org. David, while I don't see 3.3 packages I do see 3.4 snapshots in the repository. Will that not do? If there are any regressions keeping you back on 3.3 now's a good time to report them! Alp. On 06/10/2013 18:22, David Nadlinger wrote: > On Sun, Oct 6, 2013 at 6:12 PM, Konstantin Tokarev <annulen at yandex.ru> wrote: >>> It seems like the llvm-3.3-* packages are gone from the Ubuntu Precise >>> APT repository, http://llvm.org/apt/precise/. >>> >>> Is this on purpose? Any recomme...

On Sun, Oct 6, 2013 at 6:12 PM, Konstantin Tokarev <annulen at yandex.ru> wrote: >> It seems like the llvm-3.3-* packages are gone from the Ubuntu Precise >> APT repository, http://llvm.org/apt/precise/. >> >> Is this on purpose? Any recommended replacements? (Launchpad?) > > http://llvm.org/docs/GettingStarted.html#getting-started-quickly-a-summary Sorry, but

...ct and kept on llvm.org. > > David, while I don't see 3.3 packages I do see 3.4 snapshots in the > repository. Will that not do? > > If there are any regressions keeping you back on 3.3 now's a good time > to report them! > > Alp. > > On 06/10/2013 18:22, David Nadlinger wrote: > > On Sun, Oct 6, 2013 at 6:12 PM, Konstantin Tokarev <annulen at yandex.ru> > wrote: > >>> It seems like the llvm-3.3-* packages are gone from the Ubuntu Precise > >>> APT repository, http://llvm.org/apt/precise/. > >>> > >>> I...

Hi all, It seems like the llvm-3.3-* packages are gone from the Ubuntu Precise APT repository, http://llvm.org/apt/precise/. Is this on purpose? Any recommended replacements? (Launchpad?) Thanks, David

06.10.2013, 18:44, "David Nadlinger" <code at klickverbot.at>: > Hi all, > > It seems like the llvm-3.3-* packages are gone from the Ubuntu Precise > APT repository, http://llvm.org/apt/precise/. > > Is this on purpose? Any recommended replacements? (Launchpad?) http://llvm.org/docs/GettingStarted.html#g...

There is a description of all the possible linkage types at http://llvm.org/docs/LangRef.html#linkage – does this answer your question? (Basically, an extern_weak resp. ExternalWeakLinkage symbol becomes null instead of being an undefined reference) David On 3/16/11 7:06 PM, Junjie Gu wrote: > What is the difference between WeakAnyLinkage and ExternalWeakLinkage > ? They are defined

On Oct 27, 2013 2:16 PM, "David Nadlinger" <code at klickverbot.at> wrote: > > The following piece of IR is a fixed point for opt -std-compile-opts/-O3: > > --- > target datalayout = > "e-p:64:64:64-S128-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f16:16:16-f32:32:32-f64:64:64-f128:128:128-v64:64:64-v128:1...

What is the difference between WeakAnyLinkage and ExternalWeakLinkage ? They are defined in GlobalValue.h. Thanks Junjie

...nk so. There have been other reports lately related to this being >>> wrong. >>> >>> http://llvm.org/bugs/show_bug.cgi?id=14410 >>> >>> CC'ing Timur since he might know more about this. >>> >>> On Wed, Feb 20, 2013 at 5:27 PM, David Nadlinger <code at klickverbot.at> >>> wrote: >>>> >>>> On Tue, Feb 19, 2013 at 2:13 PM, Duncan Sands <baldrick at free.fr> wrote: >>>> >> My question: Is there an easy way of disabling the name-mangling part >>>> >> but keep th...

...> > David, while I don't see 3.3 packages I do see 3.4 snapshots in the > repository. Will that not do? > > If there are any regressions keeping you back on 3.3 now's a good time > to report them! > > Alp. > > On 06/10/2013 18:22, David Nadlinger wrote: > > On Sun, Oct 6, 2013 at 6:12 PM, Konstantin Tokarev > <annulen at yandex.ru <mailto:annulen at yandex.ru>> wrote: > >>> It seems like the llvm-3.3-* packages are gone from the Ubuntu > Precise > >>> APT repository, http:/...

The following piece of IR is a fixed point for opt -std-compile-opts/-O3: --- target datalayout = "e-p:64:64:64-S128-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f16:16:16-f32:32:32-f64:64:64-f128:128:128-v64:64:64-v128:128:128-a0:0:64-s0:64:64-f80:128:128-n8:16:32:64" target triple = "x86_64-unknown-linux-gnu" ; Function Attrs: nounwind readonly define i32 @get32Bits(i8*

Hi all, LDC is an LLVM-based compiler for the D programming language, which supports garbage collection and in which globals/statics are thread-local by default. Thus, we need a way to determine the memory locations used for TLS data, in order to be able to register them as GC root ranges in program startup and thread initialization code. We are currently using LLVM thread_local globals to

Hi all, I'm currently working on getting our (LDC) compiler to run on Win32/MinGW, now that DW2-style EH is available for it. The D programming language has a feature equivalent to LLVM module level inline assembly, so we need to at least partly follow the x86 D calling convention (http://dlang.org/abi.html). Most notably, the ABI mandates that the callee cleans the stack. On the various

On Mon, Oct 28, 2013 at 10:09 AM, James Courtier-Dutton <james.dutton at gmail.com> wrote: > My guess is that this is a missed optimization, but in real life, all > projects i have worked fix this in the C or C++ code using macros that > change what instructions are used based on target platform and its > endedness. One reason for writing code like this, i.e. explicitly spelling