similar to: Non-native endianness support in Clang

Displaying 19 results from an estimated 19 matches similar to: "Non-native endianness support in Clang"

2013 Jan 23
2
[LLVMdev] [cfe-dev] OpenCL SPIR/NVPTX code generation
On Jan 23, 2013, at 4:04 , "Benyei, Guy" <guy.benyei at intel.com> wrote: > Hi Ankur, > Since you use –Xclang, the clang executable passes multiple triples to “clang -cc1”. You can see that if you add the -v option. I’m sure there is someone here who can explain it better than I… > Anyhow, I think you better use clang -cc1. Make sure -cc1 is the first command line option
2018 Jan 22
2
Random Forests
Muchas gracias Carlos, como siempre. Es raro que se me pasase. En su momento miré todos los argumentos del RF, como hago siempre, pero ese lo había olvidado. La verdad es que funcionaba estupendamente, pero me parecía extraño. Aunque dado que los RF no sobreajustan, no hay problema con que sus árboles sean todo lo grandes que quieras. Lo he testado con una base de datos externa y explica
2013 Jan 24
1
[LLVMdev] [cfe-dev] OpenCL SPIR/NVPTX code generation
Hello everyone, Thanks a lot for the help. -target nvptx worked great with llvm-3.2. However it gives error with -target spir. LLVM/Clang trunk although works good for both options ( probably because spir is still work in progress ). Thanks again. - Ankur On Thu, Jan 24, 2013 at 12:43 PM, Benyei, Guy <guy.benyei at intel.com> wrote: > Hi Jordan,**** > > You’re right, and
2015 Jun 09
2
[LLVMdev] Constant folding inttoptr i32 0 to null pointer?
On Tue, Jun 9, 2015 at 12:32 PM, David Majnemer <david.majnemer at gmail.com> wrote: > 'load volatile i32 addrspace(1)* null' seems fine to me. However, it > looks like instcombine will turn: > define i32 @foo() { > entry: > %std_ld.i = load volatile i32, i32 addrspace(1)* null > ret i32 %std_ld.i > } > > into: > define i32 @foo() { > entry:
2015 Jun 09
4
[LLVMdev] Constant folding inttoptr i32 0 to null pointer?
Thanks David, It turns out, that the address space I was using was not 0, and yet the pointer was constant folded to null. Here is the sequence: Unoptimized code: define i32 @foo() #0 { entry: %address.addr.i = alloca i32, align 4 %value.i = alloca i32, align 4 store i32 0, i32* %address.addr.i, align 4 %0 = load i32* %address.addr.i, align 4 %1 = inttoptr i32 %0 to i32 addrspace(1)*
2013 Jan 24
0
[LLVMdev] [cfe-dev] OpenCL SPIR/NVPTX code generation
Hi Jordan, You're right, and the driver -target option works perfectly with the SPIR triples. Thanks Guy Benyei [email_signature_guy_new2] From: Jordan Rose [mailto:jordan_rose at apple.com] Sent: Wednesday, January 23, 2013 19:47 To: Benyei, Guy Cc: ankur deshwal; cfe-dev at cs.uiuc.edu; llvmdev at cs.uiuc.edu Subject: Re: [cfe-dev] OpenCL SPIR/NVPTX code generation On Jan 23, 2013, at
2013 Jan 23
3
[LLVMdev] OpenCL SPIR/NVPTX code generation
Hi Guy, Thanks a lot for the clarification. I tried using the triple for SPIR as $ clang -x cl -fno-builtin -emit-llvm -c -Xclang -triple -Xclang spir-unknown-unknown Simple_Kernel.cl However I get the following error. error: unknown target triple 'spir-unknown-unknown', please use -triple or -arch I also tried with triple nvptx-unknown-unknown clang -x cl -fno-builtin -emit-llvm -S
2012 Sep 19
1
[LLVMdev] [cfe-dev] SPIR Review Status: after Introduction and 32bits vs. 64bits discussions
On Wed, Sep 19, 2012 at 5:43 AM, Benyei, Guy <guy.benyei at intel.com> wrote: > Ouriel, Boaz wrote: > > > ... > > > *** Richard Smith, Eli Friedman & Nadav Rotem: Portability Issues *** > > *****comment 1: int does_this_compile[sizeof(void*) - 3]; > Answer: We are discussing this internally and will provide an answer soon. >
2012 Sep 14
2
[LLVMdev] SPIR Review Status: after Introduction and 32bits vs. 64bits discussions
Hi All, I have made an attempt to summarize the different comments that were raised so far. An answer has been provided inside. Please let me know if I missed any comments or got them wrong. *** Hal Finkel: Handling FP_CONTRACT *** *****Comment: The current specification provides a mechanism for handling FP_CONTRACT, but does so only at the module level. After much debate,
2012 Sep 19
0
[LLVMdev] [cfe-dev] SPIR Review Status: after Introduction and 32bits vs. 64bits discussions
Ouriel, Boaz wrote: ... *** Richard Smith, Eli Friedman & Nadav Rotem: Portability Issues *** *****comment 1: int does_this_compile[sizeof(void*) - 3]; Answer: We are discussing this internally and will provide an answer soon. ****comment 2: struct how_do_you_represent_this_in_IR {
2015 Jun 09
2
[LLVMdev] Constant folding inttoptr i32 0 to null pointer?
Hello, It seems that ConstantFoldCastInstruction in ConstantFold.cpp folds inttoptr instruction with 0 as operand to a null pointer. It makes sense, when talking about a C-style frontend, as the C99 spec (6.3.2.3) states: "An integer constant expression with the value 0, or such an expression cast to type void *, is called a null pointer constant." On the other hand, some architectures
2013 Jan 23
0
[LLVMdev] OpenCL SPIR/NVPTX code generation
Hi Ankur, Since you use -Xclang, the clang executable passes multiple triples to "clang -cc1". You can see that if you add the -v option. I'm sure there is someone here who can explain it better than I... Anyhow, I think you better use clang -cc1. Make sure -cc1 is the first command line option you use. $ clang -cc1 -fno-builtin -emit-llvm-bc -triple spir-unknown-unknown
2012 Dec 25
0
[LLVMdev] [cfe-commits] r170125 - /cfe/trunk/lib/Basic/Targets.cpp
Hi, Removing the data layout causes another issue: In SPIR we know the size and alignment of everything, but except the data layout string, I see no other way to update this information in the DataLayout class. This way we get a failure when trying to build the layout of a struct that contains a pointer in 32 bits. In DataLayout.cpp, the default pointer size and alignment is 8 bytes, which is
2017 Nov 22
3
Tibble o data.table?
Que es postgres y presto?? Se uqe google tiene la respuesta,.... ________________________________ De: José Luis Cañadas <canadasreche en gmail.com> Enviado: miércoles, 22 de noviembre de 2017 22:01 Para: Jesús Para Fernández Cc: Carlos Ortega; r-help-es en r-project.org Asunto: Re: [R-es] Tibble o data.table? Yo la ventaja que le veo a tibble y demás cosas del mundo tidy es la conexión a
2018 Jun 01
1
endianness and bit fields in struct{}
Good Day Is any work in the LLVM development community are pointed to expanding IR model to support bit fields and arbitrary endianness manipulations? I'm looking on LLVM as a backend for data language compilator. I'm working with IoT (Lora) and has a problem with data format specification for a wide variety of end-node devices (M2M/SmartHome). Due to the fact that the size of the
2012 Nov 06
0
[LLVMdev] SPIR BoF Session at 2012 LLVM Developers Conference
Hi All, In this session we would like to talk about SPIR size_t/ptrdiff_t approach and get feedback about it. Guy has prepared a patch that demonstrates some of the changes in Clang and we hope to have a good discussion based on it. In addition, we are interested in meeting others who care about the concept of SPIR and would like to learn more about their usages. Cheers, Boaz From:
2018 Dec 19
0
[PATCH v3 00/12] x86, kbuild: revert macrofying inline assembly code
On Wed, Dec 19, 2018 at 5:26 AM Nadav Amit <namit at vmware.com> wrote: > > > On Dec 17, 2018, at 8:03 AM, Masahiro Yamada <yamada.masahiro at socionext.com> wrote: > > > > This series reverts the in-kernel workarounds for inlining issues. > > > > The commit description of 77b0bf55bc67 mentioned > > "We also hope that GCC will eventually get
2017 Jan 06
0
Wine release 2.0-rc4
The Wine development release 2.0-rc4 is now available. What's new in this release (see below for details): - Bug fixes only, we are in code freeze. The source is available from the following locations: http://dl.winehq.org/wine/source/2.0/wine-2.0-rc4.tar.bz2 http://mirrors.ibiblio.org/wine/source/2.0/wine-2.0-rc4.tar.bz2 Binary packages for various distributions will be available
2019 Feb 08
1
Samba and ufw (mmcg29440@frontier.com)
Rowland, Thank you for all your help, I agree that this is not a Samba issue. Given rhat it works without the firewall. It' either a ufw or Windows 8.1 issue. Louis, Applied the rules you suggested to ufw exactly as written. No change. Still cannot connect with firewall enabled. Same error mesage as before "Cannot mount location ...". ufw log set to medium and copied below.