search for: set_decl_assembler_nam

...:01 AM, Bill Wendling wrote: > >> The symbols I'm interested in already have internal linkage (as you >> would expect). But because the mangler is in charge of assigning them >> names, they never seem to be decorated with the 'L' in front. . . . > > If you use SET_DECL_ASSEMBLER_NAME (something like that) you can > specify the full name for this stuff, including the L. This is how > other Objc metadata works. Yup. see start_var_decl() in objc-act.c and its uses of set_user_assembler_name(). - Devang

The symbols I'm interested in already have internal linkage (as you would expect). But because the mangler is in charge of assigning them names, they never seem to be decorated with the 'L' in front. . . . -bw On Mon, Nov 24, 2008 at 10:48 AM, Dan Gohman <gohman at apple.com> wrote: > Can symbols with external linkage but no name be converted > to have internal linkage?

On Nov 24, 2008, at 11:01 AM, Bill Wendling wrote: > The symbols I'm interested in already have internal linkage (as you > would expect). But because the mangler is in charge of assigning them > names, they never seem to be decorated with the 'L' in front. . . . If you use SET_DECL_ASSEMBLER_NAME (something like that) you can specify the full name for this stuff, including the L. This is how other Objc metadata works. -Chris

...update the list on any progress. Index: gcc/fortran/f95-lang.c =================================================================== --- gcc/fortran/f95-lang.c (revision 160) +++ gcc/fortran/f95-lang.c (working copy) @@ -713,7 +713,11 @@ TREE_PUBLIC (decl) = 1; if (library_name) SET_DECL_ASSEMBLER_NAME (decl, get_identifier (library_name)); +#ifndef ENABLE_LLVM make_decl_rtl (decl); +#else + make_decl_llvm (decl); +#endif pushdecl (decl); DECL_BUILT_IN_CLASS (decl) = class; DECL_FUNCTION_CODE (decl) = function_code; Index: gcc/fortran/trans-decl.c ===================================...

On Fri, 1 Sep 2006, Michael McCracken wrote: > Hi, I have a first quick patch and a question. The patch links f951 > with g++ when LLVM is enabled. It's at the end of this email. Thanks, applied! > I wanted to know if I should submit patches with comments around them > like the "APPLE LOCAL LLVM" ones that mark the LLVM-only changes to > the tree. I'd like to

Hi, I have a first quick patch and a question. The patch links f951 with g++ when LLVM is enabled. It's at the end of this email. I wanted to know if I should submit patches with comments around them like the "APPLE LOCAL LLVM" ones that mark the LLVM-only changes to the tree. I'd like to make it as easy as possible to apply these, so let me know any rules I should be following.