similar to: [LLVMdev] Determining TLS memory ranges

Hi Lauro, On Wed, 2007-04-11 at 15:15 -0300, Lauro Ramos Venancio wrote: > For everyone understand which code must be emitted to implement TLS, I > will paste the code generated by gcc for a simple function: ... snip ... This proposal sounds really good to me. I only have a couple comments. We have a "section" keyword already developed in LLVM assembly. Perhaps instead of

For everyone understand which code must be emitted to implement TLS, I will paste the code generated by gcc for a simple function: __thread int a = 1; int f(){ return a; } gcc teste.c -o teste.s -S -O2 (arm-linux-gnueabi): .global a .section .tdata,"awT",%progbits <== special section for tls symbols .align 2 .type a, %object

On 03.12.2013 14:30, Rafael Espíndola wrote: > Can you send a patch? Hi Rafael, the patch is attached. @Mikael, Tim Thanks for the help. I really needed only the link to the repo. Regards, Kai > > On 2 December 2013 06:44, Kai Nacke <kai at redstar.de> wrote: >> Hi! >> >> I like to submit some updates to the LLVM website regarding the LDC >> compiler. All

Reviving this thread with a patch! And some comments inline. Please take a look and let me know what you think. - Hans On Wed, Apr 25, 2012 at 12:39 PM, Hans Wennborg <hans at chromium.org> wrote: > Hi all, > > I would like to hear your thoughts on adding support for extending the > IR to allow for explicitly selecting which model to use for > thread-local storage of a

Maybe it's time to add it to the LLVM projects list. :) The original annoucement on digitalmars.D.announce and http://www.incasoftware.de/~kamm/projects/index.php/2009/01/09/ldc-09-released/ was: --- The first version of LDC (http://www.dsource.org/projects/ldc), the LLVM based compiler for version one of the D programming language has been released for x86-32 Linux. Get it here:

You need to get the LLVM Sphinx docs using SVN or Git. If you want it, I can do the changes for you since I have already everything in place. -- Mikael 2013/12/3 Kai Nacke <kai at redstar.de> > Hi Rafael, > > is there a repository with the static pages or should I simply produce a > diff between the 2 versions? > > Regards, > Kai > > On 03.12.2013 14:30,

Hi Rafael, is there a repository with the static pages or should I simply produce a diff between the 2 versions? Regards, Kai On 03.12.2013 14:30, Rafael Espíndola wrote: > Can you send a patch? > > On 2 December 2013 06:44, Kai Nacke <kai at redstar.de> wrote: >> Hi! >> >> I like to submit some updates to the LLVM website regarding the LDC >> compiler.

Can you send a patch? On 2 December 2013 06:44, Kai Nacke <kai at redstar.de> wrote: > Hi! > > I like to submit some updates to the LLVM website regarding the LDC > compiler. All links are currently out-of-date. The following pages need > updates: > > On page http://www.llvm.org/Users.html, please replace the existing entry > "LLVM D Compiler" in section

Hi all, I would like to hear your thoughts on adding support for extending the IR to allow for explicitly selecting which model to use for thread-local storage of a variable. The motivation is to allow Clang to support the "tls_model" variable attribute [1], as requested in PR9788. The idea would be to extend the IR to allow an optional TLS-model argument to the thread_local

Hi all, System: x86-64 ubuntu 11.04 LLVM: 3.0 gcc: 4.5.2 I declare a thread_local global variable and access it in a function in llvm IR. for example, @my_value = linkonce thread_local global %dummy* null define void @test1() { entry: %load_my_value = load %dummy** @my_value .... } After that, I use the following command: bash$ llc -relocation-model=pic test.ll And I have test.s

Hi! I like to submit some updates to the LLVM website regarding the LDC compiler. All links are currently out-of-date. The following pages need updates: On page http://www.llvm.org/Users.html, please replace the existing entry "LLVM D Compiler" in section "Open Source Projects" with: <tr> <td><a href="http://wiki.dlang.org/LDC/">

I'm learning the xray library and try if it can be built on windows, in xray_fdr_logging_impl.h line 152 , comment written as // Using pthread_once(...) to initialize the thread-local data structures but at line 175, 183, code written as thread_local pthread_key_t key; // Ensure that we only actually ever do the pthread initialization once. thread_local bool UNUSED Unused = [] {

On Sun, Dec 4, 2011 at 9:18 AM, Kai <kai at redstar.de> wrote: > Hi! > > LLVM currently does not implement the implicit TLS model on Windows. This > model is easy: > > - a thread local variable ends up in the .tls section > - to access a thread local variable, you have to do >  (1) load pointer to thread local storage from TEB >      On x86_64, this is gs:0x58, on

> On 2018-12-07 22:30, Ken Cunningham via llvm-dev wrote: >> Please excuse hobbiest-level question. >> Darwin 11+ enables thread_local variables using system-level supports. >> I have an interest in enabling TLS on darwin < 11 using emulated-tls. > > Is anyone still running macOS 10.6 or older? > > -- > /Jacob Carlborg > [off topic, apologies] Yes,

I don't remember anything other that what I've written in the bug João has mentioned. Probably something like this patch http://llvm.org/bugs/show_bug.cgi?id=14410#c6 ? 2013/2/20 Joã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

On Oct 27, 2008, at 11:03 PM, Kelly W wrote: > Hello everyone, > > I just thought I would let people here know that ldc (llvm backend > for the D Programming Language) is getting pretty usable (a few > larger libraries compile) and it now has x86-64 support added. I > decided to run some timings on some D and C++ code to compare ldc to > dmd (the mainline compiler),

Please excuse hobbiest-level question. Darwin 11+ enables thread_local variables using system-level supports. I have an interest in enabling TLS on darwin < 11 using emulated-tls. This can be enabled with a few modest patches: ========================== --- a/include/llvm/ADT/Triple.h.orig 2018-10-02 17:38:10.000000000 -0700 +++ b/include/llvm/ADT/Triple.h 2018-10-02 17:38:58.000000000

Hello everyone, I just thought I would let people here know that ldc (llvm backend for the D Programming Language) is getting pretty usable (a few larger libraries compile) and it now has x86-64 support added. I decided to run some timings on some D and C++ code to compare ldc to dmd (the mainline compiler), gdc (the gcc based D compiler) and g++. I used a ray tracing program found in this

Frits van Bommel skrev: > Benjamin Kramer wrote: > >> At the moment llvm-config outputs "2.6svn" if llvm is build from trunk >> >> $ llvm-config --version >> 2.6svn >> >> Some external projects (built out-of-tree) need to know which revision >> of llvm is installed. LDC currently asks llvm-config --src-root for the >> source

On Thu, Jul 6, 2017 at 1:35 AM, Nicholas Wilson < iamthewilsonator at hotmail.com> wrote: > Luís, try using the -no-integrated-as flag to execute the assembler for > you. > We should probably make that the default for MSP430. > Cool. When I did that on macOS, LDC generated a lot of complaints, possibly because it is assuming mach-o files. I tried changing from -mtriple=msp430