Displaying 11 results from an estimated 11 matches for "defaultvisibility".
2009 Jul 18
2
[LLVMdev] Where does llvm.memcpy.i64 and friends get lowered ?
I am iterating through Modules symbols for 'test/CodeGen/X86/memcpy.bc
I get :-
---------- Functions ----------
llvm.memcpy.i64
Mangled name = llvm.memcpy.i64
DefaultVisibility
ExternalLinkage - Externally visible.
my_memcpy
Mangled name = my_memcpy
DefaultVisibility
ExternalLinkage - Externally visible.
my_memcpy2
Mangled name = my_memcpy2
DefaultVisibility
ExternalLinkage - Externally visible.
abort
Mangled...
2009 Jul 18
3
[LLVMdev] Where does llvm.memcpy.i64 and friends get lowered ?
...t
all modules even if it is not being used. I am using GlobalValue::getUses()
to filter it. Whats going on with 'abort' ?
Aaron
>
> -Chris
>
>
> I get :-
>
> ---------- Functions ----------
> llvm.memcpy.i64
> Mangled name = llvm.memcpy.i64
> DefaultVisibility
> ExternalLinkage - Externally visible.
> my_memcpy
> Mangled name = my_memcpy
> DefaultVisibility
> ExternalLinkage - Externally visible.
> my_memcpy2
> Mangled name = my_memcpy2
> DefaultVisibility
> ExternalLinkag...
2009 Jul 18
0
[LLVMdev] Where does llvm.memcpy.i64 and friends get lowered ?
...:
> I am iterating through Modules symbols for 'test/CodeGen/X86/memcpy.bc
If you're iterating over functions, just ignore all intrinsics.
-Chris
>
> I get :-
>
> ---------- Functions ----------
> llvm.memcpy.i64
> Mangled name = llvm.memcpy.i64
> DefaultVisibility
> ExternalLinkage - Externally visible.
> my_memcpy
> Mangled name = my_memcpy
> DefaultVisibility
> ExternalLinkage - Externally visible.
> my_memcpy2
> Mangled name = my_memcpy2
> DefaultVisibility
> ExternalLinkag...
2009 Jul 18
3
[LLVMdev] Where does llvm.memcpy.i64 and friends get lowered ?
Hi,
I am working on the COFF backend and am wondering where llvm.memcpy gets
lowered to memcpy ?
It seems to be done by the assembler backends and would have thought
it would either be done by a lowering pass or done by the mangler but it
does not seem to be either.
Many thanks in advance,
Aaron
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2009 Jul 18
0
[LLVMdev] Where does llvm.memcpy.i64 and friends get lowered ?
On Sat, Jul 18, 2009 at 2:21 PM, Aaron
Gray<aaronngray.lists at googlemail.com> wrote:
> I am working on the COFF backend and am wondering where llvm.memcpy gets
> lowered to memcpy ?
It's done by ISel. See SelectionDAG::getMemcpy.
-Eli
2016 Apr 20
2
Dead (or untested?) code in the gold plugin
...520,15 +518,9 @@ static ld_plugin_status claim_file_hook(const
ld_plugin_input_file *file,
Res.IsLinkonceOdr &= GV->hasLinkOnceLinkage();
Res.Visibility = getMinVisibility(Res.Visibility, GV->getVisibility());
switch (GV->getVisibility()) {
- case GlobalValue::DefaultVisibility:
- sym.visibility = LDPV_DEFAULT;
- break;
case GlobalValue::HiddenVisibility:
sym.visibility = LDPV_HIDDEN;
break;
- case GlobalValue::ProtectedVisibility:
- sym.visibility = LDPV_PROTECTED;
- break;
}
}
all the tests still pas...
2009 Jul 27
0
[LLVMdev] PROPOSAL : Introduce NamedMetadata
...plicitly typed as metadata. LLVM bitcode
> reader and writer will keep track of NamedMetadata in a Module. A
> module can use metadata that is not listed in any NamedMetadata value.
> A module can have multiple NamedMetadata values. NamedMetadata
> implicitly uses AppendingLinkage.
And DefaultVisibility and a default Section and an Alignment of 1?
GlobalValues carry some amount of baggage here.
Dan
2009 Jul 27
4
[LLVMdev] PROPOSAL : Introduce NamedMetadata
In LLVM IR metadata is used to attach auxiliary information with
various IR constructs. Currently metadata information is represented
using MDNode and MDString. The metadata can refer to LLVM values but
these references are not counted as regular "uses" of these values
because metadata is maintained 'on the side'. This ensures that the
optimizer is not influenced by auxiliary
2009 Jul 27
2
[LLVMdev] PROPOSAL : Introduce NamedMetadata
...a. LLVM bitcode
>> reader and writer will keep track of NamedMetadata in a Module. A
>> module can use metadata that is not listed in any NamedMetadata value.
>> A module can have multiple NamedMetadata values. NamedMetadata
>> implicitly uses AppendingLinkage.
>
> And DefaultVisibility and a default Section and an Alignment of 1?
> GlobalValues carry some amount of baggage here.
I checked these three. The code generator does not generate any code
for these NamedMetadata so we can just use vanilla default values here
without any harm.
-
Devang
2017 Apr 04
3
RFC: Adding a string table to the bitcode format
On Tue, Apr 4, 2017 at 12:36 PM, Duncan P. N. Exon Smith <
dexonsmith at apple.com> wrote:
>
> On 2017-Apr-04, at 12:12, Peter Collingbourne <peter at pcc.me.uk> wrote:
>
> On Mon, Apr 3, 2017 at 8:13 PM, Mehdi Amini <mehdi.amini at apple.com> wrote:
>
>>
>> On Apr 3, 2017, at 7:08 PM, Peter Collingbourne <peter at pcc.me.uk> wrote:
>>
2014 Nov 03
8
[LLVMdev] [PATCH] Protection against stack-based memory corruption errors using SafeStack
..., and so it requires a custom
diff --git a/include/clang/Basic/LangOptions.def b/include/clang/Basic/LangOptions.def
index e3adaec..b7f4ec1 100644
--- a/include/clang/Basic/LangOptions.def
+++ b/include/clang/Basic/LangOptions.def
@@ -192,7 +192,7 @@ ENUM_LANGOPT(ValueVisibilityMode, Visibility, 3, DefaultVisibility,
"value symbol visibility")
ENUM_LANGOPT(TypeVisibilityMode, Visibility, 3, DefaultVisibility,
"type symbol visibility")
-ENUM_LANGOPT(StackProtector, StackProtectorMode, 2, SSPOff,
+ENUM_LANGOPT(StackProtector, StackProtectorMode, 3, SSPOff,...