search for: pushdecl

...ang.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 =================================================================== --- gcc/fortran/trans-decl.c (revision 160) +++ gcc/fortran/trans-decl.c (working copy) @@ -1334,7 +...

...ooks.diff Apple made some backend changes that assume a C-like front-end (C, C++ or ObjC): calls are made to decl_constant_value, iasm_build_bracket and similar routines that mostly aren't defined by the Ada, fortran and java front-ends. However two of the calls, to c_common_type_for_mode and pushdecl, could equivalently be made to a langhook. This patch switches these to langhook calls. 2-stubs.diff This adds a new file that provides dummy implementations for all the routines mentioned in (1) that can't be turned into langhook calls. Putting these in one place means that Ada, java and f...

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

...e some backend changes that assume a C-like > front-end (C, C++ or ObjC): calls are made to decl_constant_value, > iasm_build_bracket and similar routines that mostly aren't defined > by the Ada, fortran and java front-ends. However two of the calls, > to c_common_type_for_mode and pushdecl, could equivalently be made > to a langhook. This patch switches these to langhook calls. > > 2-stubs.diff > This adds a new file that provides dummy implementations > for all the routines mentioned in (1) that can't be turned into > langhook calls. Putting these in one pla...

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.