Displaying 20 results from an estimated 4000 matches similar to: "GlobalValue::AvailableExternallyLinkage"
2016 Nov 19
4
GlobalValue::AvailableExternallyLinkage
Thanks Mehdi.
My pass clones the functions within a module in order to have the original function and an exact copy of the same function but with a different name, i.e. sum() and sum_parallel().
After my pass I will run ThreadSanitizer instrumentation pass only on the new copy of the functions, i.e. only the “_parallel” functions will be instrumented by tsan.
In some programs that I am
2016 Nov 19
2
GlobalValue::AvailableExternallyLinkage
Because what is happening is that if function “atoi” gets cloned I don’t have a definition of “atoi_parallel” therefore I get undefined references when linking.
I just want to clone and instrument functions implemented in modules of my program.
> On Nov 19, 2016, at 13:54, Mehdi Amini <mehdi.amini at apple.com> wrote:
>
>
>> On Nov 19, 2016, at 12:44 PM, Simone Atzeni
2016 Nov 20
2
GlobalValue::AvailableExternallyLinkage
>
> On Nov 19, 2016, at 14:09, Mehdi Amini <mehdi.amini at apple.com> wrote:
>
> I assume from your description that you are also updating call sites in the same module so that if foo was calling atoi, after cloning you have foo_parallel that is calling atoi_parallel?
> If this is the issue, it depends, I’d probably consider turning the available_externally into internal.
2015 Jul 14
3
[LLVMdev] RFC: ThinLTO Symbol Linkage and Renaming
As mentioned in the Updated ThinLTO RFC (
http://lists.cs.uiuc.edu/pipermail/llvmdev/2015-May/086211.html), I am
sending the symbol linkage and renaming required by ThinLTO as a separate
RFC. It is included below. I've also attached the doc in pdf form, since
the formatting (especially for the table at the end) may not come through
in the copied text below well.
Thanks!
Teresa
ThinLTO
2015 May 19
2
[LLVMdev] Removing AvailableExternal values in GlobalDCE (was Re: RFC: ThinLTO Impementation Plan)
On Fri, May 15, 2015 at 11:20 PM, Teresa Johnson <tejohnson at google.com> wrote:
> On Fri, May 15, 2015 at 2:52 PM, David Blaikie <dblaikie at gmail.com> wrote:
>>
>>
>> On Fri, May 15, 2015 at 1:15 PM, Teresa Johnson <tejohnson at google.com>
>> wrote:
>>>
>>> On Fri, May 15, 2015 at 10:04 AM, David Blaikie <dblaikie at
2015 Feb 25
2
[LLVMdev] Walking thru CallGraph bottom up
Thanks John.
I guess I will use a ModulePass, so when I am implementing the “runOnModule” function,
do I have to loop through all the functions, for each functions all the BasicBlocks and for each BasicBlock all the instructions
or given the Module I have to call the CallGraph directly?
Is there an example out there? I can’t find anything.
Thanks.
Simone
> On Feb 24, 2015, at 13:29, John
2015 Feb 24
2
[LLVMdev] Walking thru CallGraph bottom up
Hi all,
I would like to create a Pass that given an IR instruction walks starting from that instruction up to the main function
to identify all the functions call that have been made to call that instruction.
Is it possible? What kind of Pass should I create?
Thanks
Best,
Simone
Simone Atzeni
simone.at at gmail.com
+1 (801) 696-8373
2015 Jul 21
1
[LLVMdev] RFC: ThinLTO Symbol Linkage and Renaming
Thanks for the comments! Responses below.
Teresa
On Tue, Jul 21, 2015 at 1:06 PM, Duncan P. N. Exon Smith <
dexonsmith at apple.com> wrote:
>
> > On 2015-Jul-14, at 13:33, Teresa Johnson <tejohnson at google.com> wrote:
> >
> > As mentioned in the Updated ThinLTO RFC (
> http://lists.cs.uiuc.edu/pipermail/llvmdev/2015-May/086211.html), I am
> sending the
2010 Oct 29
2
[LLVMdev] "multiple definition of .. " in clang 2.8
Hi,
I tried to run the SPEC benchmark suite SPECCPU 2006 with llvm and clang
2.8. When building the perlbench sources I get these errors (see below) for
all the source files. I used a config file (
http://old.nabble.com/file/p30085184/llvm.cfg llvm.cfg ) where I specify
clang as the compiler. I verified the same sources with llvm-gcc and it
works fine. Also, I verified the sjeng benchmark from
2018 May 15
2
Pass segmentation fault after llvm_shutdown.
I ran into a similar problem a while ago; see
https://reviews.llvm.org/D30107 and https://reviews.llvm.org/D33515 .
You get the unusual stack trace because it's trying to call a destructor
in shared library which was already unloaded.
I thought we had fixed that, but maybe not? Looking again, it looks
like the patch got reverted and I didn't notice.
-Eli
On 5/14/2018 10:18 PM,
2015 Nov 25
4
Compiling for AARCH64 (VMA=42)
Hi,
I am trying to compile LLVM for AARCH (VMA=42), here my cmake command:
cmake -G "Ninja" -D SANITIZER_AARCH64_VMA=42 ..
But I get the following warning:
------------------------------------------------------------------------------------------
CMake Warning:
Manually-specified variables were not used by the project:
SANITIZER_AARCH64_VMA
2015 May 19
2
[LLVMdev] Removing AvailableExternal values in GlobalDCE (was Re: RFC: ThinLTO Impementation Plan)
On Tue, May 19, 2015 at 12:41 PM, David Blaikie <dblaikie at gmail.com> wrote:
>
>
> On Mon, May 18, 2015 at 9:09 PM, Teresa Johnson <tejohnson at google.com>
> wrote:
>>
>> On Fri, May 15, 2015 at 11:20 PM, Teresa Johnson <tejohnson at google.com>
>> wrote:
>> > On Fri, May 15, 2015 at 2:52 PM, David Blaikie <dblaikie at gmail.com>
2015 Feb 27
2
[LLVMdev] Walking thru CallGraph bottom up
Hi Simon,
> From: Simone Atzeni <simone.at at gmail.com>
> To: John Criswell <jtcriswel at gmail.com>
> Cc: llvmdev at cs.uiuc.edu
> Subject: Re: [LLVMdev] Walking thru CallGraph bottom up
> Message-ID: <318EBA41-2040-4EFE-B330-5813C817C2A2 at gmail.com>
> Content-Type: text/plain; charset="windows-1252"
>
> I think I got it and the example is
2008 Feb 16
2
[LLVMdev] linux/x86-64 codegen support
Interestingly, in the .i file there are 2 __builtin_alloca, and
EmitBuiltinAlloca is only being called once.
Andrew
On 2/16/08, Andrew Lenharth <andrewl at lenharth.org> wrote:
> libcpp/charset.c:631 turns into:
>
> %tmp16 = tail call i64 @strlen( i8* %to ) nounwind readonly
> ; <i64> [#uses=1]
> %tmp18 = tail call i64 @strlen( i8* %from ) nounwind
2015 Feb 25
0
[LLVMdev] Walking thru CallGraph bottom up
On 2/25/15 10:51 AM, Simone Atzeni wrote:
> Thanks John.
>
> I guess I will use a ModulePass, so when I am implementing the “runOnModule” function,
> do I have to loop through all the functions, for each functions all the BasicBlocks and for each BasicBlock all the instructions
If you know the Instruction, you can get it's basic block using
Instruction::getParent(), and then get
2018 May 17
0
Pass segmentation fault after llvm_shutdown.
It's working with trunk though. Do you think the patch will end up in
6.0.1?
Thanks.
Simone
On Tue, May 15, 2018 at 11:18 AM, Friedman, Eli <efriedma at codeaurora.org>
wrote:
> I ran into a similar problem a while ago; see https://reviews.llvm.org/
> D30107 and https://reviews.llvm.org/D33515 . You get the unusual stack
> trace because it's trying to call a destructor
2014 Jun 23
2
[LLVMdev] Call an analysis pass inside a tool pass
Hi,
as in the subject, is it possible to call on of the analysis pass present in the LLVM (lib/ folder) within a tool pass (tools/ folder)?
Thanks.
Best,
Simone
2017 Feb 15
2
Problem using Boost Filesystem with Clang
Hi,
not sure if this is the right place, but I am experiencing a problem using clang++ (3.9.1) with Boost Filesystem.
I have this simple program:
------------------------------------------------------------------------
#include <iostream>
#include <boost/filesystem.hpp>
using namespace boost::filesystem;
int main(int argc, char* argv[])
{
if (argc < 2)
{
std::cout
2018 May 15
2
Pass segmentation fault after llvm_shutdown.
Hi all,
I was porting my pass from LLVM 4.0 to 6.0 and I am getting a segmentation
fault.
I was able to obtain only the info below from GDB.
I tried to debug with some printf and the runOnFunction runs correctly.
Any idea/suggestion about what is going on?
The source code of the pass is here:
https://github.com/PRUNERS/sword/blob/master/lib/Sword.cpp
Any help is much appreciated,
Thanks!
2018 Jan 26
3
CMake warning when compiling Clang/LLVM
Hi,
when I run cmake I get the following warning:
---------------------------------------------------------------------------------------
CMake Warning at cmake/modules/HandleLLVMStdlib.cmake:24 (message):
Can't specify libc++ with '-stdlib='
Call Stack (most recent call first):
cmake/config-ix.cmake:15 (include)
CMakeLists.txt:580 (include)