search for: mlongcall

...;" \ BUILD_PREFIX_1="" \ LANGUAGES="" \ LIBGCC2_CFLAGS=" " \ LIBGCC2_STATIC_CFLAGS="" \ MULTILIB_CFLAGS="" T= crt3.o gmake[1]: Entering directory `/Users/ggreif/obj/gcc' # APPLE LOCAL use -mlongcall for large text support DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -isystem ./include -I. -I. -I/Users/ggreif/llvm-gcc/gcc -I/Users/ggreif/llvm-gcc/gcc/. -I/Users/ggreif/llvm-gcc/gcc/../include -I./../intl -I/Users/ggreif/llvm-gcc/gcc/../lib...

...>> g++ -o mybundle.bundle -bundle mybundle.o -lotherlibrary >> >> I get the following error: >> ld: 32-bit pic-base out of range in somefunction(Array<unsigned >> char, 40ul> const&)from mybundle.o >> >> Normally I'd try to build with the -mlongcall option, but it >> doesn't appear that llc has support for this. Is there some way to >> get llc to generate "long calls"? > > I thought that -mlongcall was a linker option? Have you tried > passing it to GCC/G++ when you link the .s file? -mlongcall is de...

...tcode.o gcc -arch ppc -c -x assembler -o mybundle.o mybundle.s g++ -o mybundle.bundle -bundle mybundle.o -lotherlibrary I get the following error: ld: 32-bit pic-base out of range in somefunction(Array<unsigned char, 40ul> const&)from mybundle.o Normally I'd try to build with the -mlongcall option, but it doesn't appear that llc has support for this. Is there some way to get llc to generate "long calls"? Thanks!

...ssembler -o mybundle.o mybundle.s > g++ -o mybundle.bundle -bundle mybundle.o -lotherlibrary > > I get the following error: > ld: 32-bit pic-base out of range in somefunction(Array<unsigned char, 40ul> const&)from mybundle.o > > Normally I'd try to build with the -mlongcall option, but it doesn't appear that llc has support for this. Is there some way to get llc to generate "long calls"? I thought that -mlongcall was a linker option? Have you tried passing it to GCC/G++ when you link the .s file? -Chris

...PREFIX_1="" \ > LANGUAGES="" \ > LIBGCC2_CFLAGS=" " \ > LIBGCC2_STATIC_CFLAGS="" \ > MULTILIB_CFLAGS="" T= crt3.o > gmake[1]: Entering directory `/Users/ggreif/obj/gcc' > # APPLE LOCAL use -mlongcall for large text support > DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -isystem ./include -I. -I. -I/Users/ggreif/llvm-gcc/gcc -I/Users/ggreif/llvm-gcc/gcc/. > -I/Users/ggreif/llvm-gcc/gcc/../include -I./../intl -I/Users/ggreif/llvm-gcc/...

.... > > Whenever I have had problems building llvm-gcc, I usually have to delete > my install and obj dir, make clean llvm, and start over from the top. > Its a pain, but it works usually. Yeah, this is what I did, everything is pretty fresh. I even grepped for "# APPLE LOCAL use -mlongcall" but no avail. It is hiding well :-( Gabor > > -Tanya > > > > > > > After following all the instructions, make gets stuck while: > > > ggreif$ gmake > > gmake \ > >          CFLAGS="-g  -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmi...

...rce/gcc/. -I../../llvm-gcc4-1.9.source/gcc/../include -I../../llvm-gcc4-1.9.source/gcc/../libcpp/include -I/opt/local/include -I/opt/local/include -I/opt/local/var/db/dports/build/_unencrypted_erickt_Projects_macports-trunk_dports_lang_llvm/work/llvm-1.9/include -I/opt/local/lib/llvm/include -mlongcall \ -c ../../llvm-gcc4-1.9.source/gcc/config/darwin-crt2.c -o crt2.o make \ CFLAGS="-g -O2 -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wold-style-definition " \ CONFIG_H="config.h auto-host.h ../../llvm-gcc...

Hi Owen, I'm seeing this failure on one of my machines -- PPC G5: $ # APPLE LOCAL use -mlongcall for large text support /Volumes/SandBox/Clean/bug/llvm-gcc.obj/./gcc/xgcc -B/Volumes/SandBox/Clean/bug/llvm-gcc.obj/./gcc/ -B/Volumes/SandBox/Clean/bug/llvm-gcc.install/powerpc-apple-darwin9.1.0/bin/ -B/Volumes/SandBox/Clean/bug/llvm-gcc.install/powerpc-apple-darwin9.1.0/lib/ -isystem /Volumes/Sand...

...+++ llvm-gcc-4.2/trunk/gcc/config/i386/darwin.h 2008/10/02 06:16:08 56946 @@ -101,6 +101,8 @@ %{!mmacosx-version-min=*: %{!miphoneos-version-min=*: %(darwin_cc1_minversion)}} \ "/* APPLE LOCAL ignore -mcpu=G4 -mcpu=G5 */"\ %<faltivec %<mno-fused-madd %<mlong-branch %<mlongcall %<mcpu=G4 %<mcpu=G5 \ + "/* APPLE LOCAL enable format security warnings */"\ + %{!Wno-format:-Wformat -Wformat-security} \ %{g: %{!fno-eliminate-unused-debug-symbols: -feliminate-unused-debug-symbols }}" /* APPLE LOCAL AltiVec */ followed by a fixed that claims not t...

...lvmgcc42.roots/llvmgcc42~obj/src/gcc/libgcc2.c:1193: internal compiler error: Abort trap Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://developer.apple.com/bugreporter> for instructions. make[5]: *** [libgcc/./_ucmpdi2.o] Error 1 # APPLE LOCAL use -mlongcall for large text support /Volumes/Sandbox/Buildbot/llvm/build.llvm-gcc-x86_64-darwin10-selfhost/ llvmgcc42.roots/llvmgcc42~obj/obj-i686-i686/./gcc/xgcc -B/Volumes/ Sandbox/Buildbot/llvm/build.llvm-gcc-x86_64-darwin10-selfhost/ llvmgcc42.roots/llvmgcc42~obj/obj-i686-i686/./gcc/ -B/Developer/usr/ l...

...../include > -I../../llvm-gcc4-1.9.source/gcc/../libcpp/include -I/opt/local/ > include > -I/opt/local/include > -I/opt/local/var/db/dports/build/ > _unencrypted_erickt_Projects_macports-trunk_dports_lang_llvm/work/ > llvm-1.9/include > -I/opt/local/lib/llvm/include \ > -mlongcall \ > -c ../../llvm-gcc4-1.9.source/gcc/config/darwin-crt3.c -o crt3.o

...tribute or a string based key value pair is an > interesting discussion. Also, would we want to, instead, expose the backend > options as clang IR level options? Seems to make sense from that > perspective and then they can add the appropriate attributes to the > functions themselves. (-mlongcalls for the long calls option for example). > > Thanks! > > -eric > > On Tue Nov 18 2014 at 12:26:49 PM Akira Hatanaka <ahatanak at gmail.com> > wrote: > >> Updated patch is attached. Note this is just a work-in-progress patch and >> I plan to address the feed...

Updated patch is attached. Note this is just a work-in-progress patch and I plan to address the feedback comments later if this patch is in the right direction. This is how the command line options are parsed and used by the backend passes: 1. Tools such as clang and llc call cl::ParseCommandLineOptions. Any of the options that should be written to the bitcode as function or module attributes

...xposed as an llvm attribute or a string based key value pair is an interesting discussion. Also, would we want to, instead, expose the backend options as clang IR level options? Seems to make sense from that perspective and then they can add the appropriate attributes to the functions themselves. (-mlongcalls for the long calls option for example). > > Thanks! > > -eric Again, I think we can evaluate specific options on a case-by-case basis. For some of them, it might make sense to expose them as clang options. Like you, I had previously assumed we would teach the front-end about all the...

...xposed as an llvm attribute or a string based key value pair is an interesting discussion. Also, would we want to, instead, expose the backend options as clang IR level options? Seems to make sense from that perspective and then they can add the appropriate attributes to the functions themselves. (-mlongcalls for the long calls option for example). >> >> Thanks! >> >> -eric > > Again, I think we can evaluate specific options on a case-by-case basis. For some of them, it might make sense to expose them as clang options. Like you, I had previously assumed we would teach t...

...an interesting discussion. Also, would we want to, instead, >>>>> expose the backend options as clang IR level options? Seems to make sense >>>>> from that perspective and then they can add the appropriate attributes to >>>>> the functions themselves. (-mlongcalls for the long calls option for >>>>> example). >>>>> >>>>> Thanks! >>>>> >>>>> -eric >>>>> >>>> >>> Again, I think we can evaluate specific options on a case-by-case basis. >>> Fo...

...on. Also, would we want to, instead, >>>>>>> expose the backend options as clang IR level options? Seems to make sense >>>>>>> from that perspective and then they can add the appropriate attributes to >>>>>>> the functions themselves. (-mlongcalls for the long calls option for >>>>>>> example). >>>>>>> >>>>>>> Thanks! >>>>>>> >>>>>>> -eric >>>>>>> >>>>>> >>>>> Again, I think we can ev...

...to, instead, >>>>>>>>> expose the backend options as clang IR level options? Seems to make sense >>>>>>>>> from that perspective and then they can add the appropriate attributes to >>>>>>>>> the functions themselves. (-mlongcalls for the long calls option for >>>>>>>>> example). >>>>>>>>> >>>>>>>>> Thanks! >>>>>>>>> >>>>>>>>> -eric >>>>>>>>> >>>>>&g...

....4.source/gcc/config/i386/darwin.h 2008-11-01 23:00:37.000000000 -0400 @@ -101,8 +101,6 @@ %{!mmacosx-version-min=*: %{!miphoneos-version-min=*: %(darwin_cc1_minversion)}} \ "/* APPLE LOCAL ignore -mcpu=G4 -mcpu=G5 */"\ %<faltivec %<mno-fused-madd %<mlong-branch %<mlongcall %<mcpu=G4 %<mcpu=G5 \ - "/* APPLE LOCAL enable format security warnings */"\ - %{!Wno-format:-Wformat -Wformat-security} \ %{g: %{!fno-eliminate-unused-debug-symbols: -feliminate-unused-debug-symbols }}" /* APPLE LOCAL AltiVec */ to allow gfortran to build and compile...