similar to: [LLVMdev] configure testing for linker flags using llvm-gcc

On Wed, May 17, 2017 at 1:32 PM, Rui Ueyama via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On Wed, May 17, 2017 at 1:11 PM, Petr Hosek <phosek at chromium.org> wrote: > >> The motivation is not only memory savings but also security: >> can-never-be-written is strictly better than RELRO in all cases. The >> biggest win is when .dynamic is the sole reason

Forgot to mention. I don't know how well the canadian cross compile stuff works in 2.5. We made some improvements in that area for 2.6. If you have trouble with it, I'd suggest trying 2.6 (or even better, ToT svn) and seeing if things are improved there. -Jim On Sep 25, 2009, at 2:04 AM, Martins Mozeiko wrote: > Hello. > > My goal is to use LLVM with JIT compiler for ARM

Hello. My goal is to use LLVM with JIT compiler for ARM on Android device. Currently I have successfully built and executed LLVM bitcode with interpreter on Android. Speed is not so great, that is why I want to use JIT. I tried building bitcode on windows with llvm-gcc that is provided on llvm home page. Resulting bitcode runs great in interpreter, but it doesn't use JIT. From what I

I am trying to build llvm-gcc4.2-2.6. My configure options are $ /local/tools/lin32/llvm-gcc4.2-2.6/bin/llvm-gcc -v Using built-in specs. Target: i686-linux Configured with: ../llvm-gcc4.2-2.6.source/configure --prefix=/local/tools/lin32/llvm-gcc4.2-2.6 --disable-nls --enable-shared --enable-threads=posix --enable-languages=c,c++ --with-gnu-as --with-gnu-ld --target=i686-linux

On Thu, Aug 29, 2019 at 3:10 AM Fāng-ruì Sòng <maskray at google.com> wrote: > Hello Vic, > > To make sure I understand the proposal correctly, do you propose: > > Old: R RX RW(RELRO) RW > New: R(R+RELRO) RX RW; R includes the traditional R part and the > RELRO part > Runtime (before relocation resolving): RW RX RW > Runtime (after relocation resolving): R RX

Hey all, TL;DR: Moving RELRO segment to be immediately after read-only segment so that the dynamic linker has the option to merge the two virtual memory areas at run time. This is an RFC for moving RELRO segment. Currently, lld orders ELF sections in the following order: R, RX, RWX, RW, and RW contains RELRO. At run time, after RELRO is write-protected, we'd have VMAs in the order of: R, RX,

Hello Vic, I don't have a lot to add myself. I think that majority of the input needs to come from the OS stakeholders. My main concern is if it requires work on every platform to take advantage or avoid regressions then perhaps it is worth adding as an option rather than changing the default. Some questions: - Does this need work in every OS for correctness of programs? For example you

Hi, every body, I get stuck when trying to build llvm-gcc4.2-2.4 on x86_64 Linux with GCC-4.3.3. I meet this error: make[3]: Entering directory `/home/wangtielei/TOOLS/llvm/llvm-gcc-obj/gcc' /home/wangtielei/TOOLS/llvm/llvm-gcc-obj/./prev-gcc/xgcc -B/home/wangtielei/TOOLS/llvm/llvm-gcc-obj/./prev-gcc/ -B/usr/local/x86_64-unknown-linux-gnu/bin/ -c -g -O2 -DIN_GCC -W -Wall -Wwrite-strings

>> Dear All, I have been trying for days but still cannot break this barrier. May I get your help? I have compiled llvm-2.1 successfully and make install. When I proceed with llvm-gcc-4.2-2.1, however, I keep getting linking error as attached. Some functions with totally different content conflict with each other in linking process. That is a Linux box (Debian, with 2.6.23-1

I first install the gcc-4.2.4 . then I set CC and CXX export CC= "path of my gcc-4.2.4" export CXX="path of my g++-4.2.4" after that , I config and make . error occur like this : /home/ws/software/gcc-4-2/bin/gcc -c -g -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros

On Fri, Aug 30, 2019 at 4:54 AM Fāng-ruì Sòng <maskray at google.com> wrote: > > > Old: R RX RW(RELRO) RW > > > New: R(R+RELRO) RX RW; R includes the traditional R part and the > > > RELRO part > > > Runtime (before relocation resolving): RW RX RW > > > Runtime (after relocation resolving): R RX RW > > > > > I actually see two

Not sure if that's related, but we had two failures last night as well: MacOS/Universal build failed on rev 54197, when building the x86->ppc cross: cc1: warnings being treated as errors /Users/julien/buildbot/llvm/gcc-build/src/gcc/cp/pt.c:5296: warning: no previous prototype for 'outermost_tinst_level' make[2]: *** [cp/pt.o] Error 1 MingW failed on rev 54208:

Hi John, > I am trying to build llvm-gcc4.2-2.6. > > My configure options are > > $ /local/tools/lin32/llvm-gcc4.2-2.6/bin/llvm-gcc -v > Using built-in specs. > Target: i686-linux > Configured with: ../llvm-gcc4.2-2.6.source/configure --prefix=/local/tools/lin32/llvm-gcc4.2-2.6 --disable-nls --enable-shared --enable-threads=posix --enable-languages=c,c++ --with-gnu-as

Hi. Sorry for reposting my mail, but can somebody at lest give some general ideas for what to look to solve my problem? -- Martins Mozeiko Begin forwarded message: > From: Martins Mozeiko <49640f8a at gmail.com> > Date: September 25, 2009 12:04:04 GMT+03:00 > To: llvmdev at cs.uiuc.edu > Subject: JIT on ARM > > Hello. > > My goal is to use LLVM with JIT compiler

Hello all, I am trying to install the llvm-gcc front end to use it in one of my projects, but I got stuck.. I am working on a Sun workstation: SunOS xxx 5.10 Generic_137137-09 sun4u sparc SUNW,Sun-Fire-V240 and I have gcc version 3.4.6: Reading specs from /sw/gcc-3.4.6/lib/gcc/sparc-sun-solaris2.10/3.4.6/specs Configured with: /.scratch/andjo/lsw/src/gcc/gcc-3.4.6/configure

Hi, I am having some difficulties building llvm on Itanium. My procedure for building LLVM is: cd /liberty/llvm.ia64/llvm-2.1 ./configure make ENABLE_OPTIZED=1 cd /liberty/llvm.ia64/obj /liberty/llvm.ia64/llvm-gcc4.2-2.1.source/configure --prefix=/liberty/llvm.ia64/install --enable-llvm=/liberty/llvm.ia64/llvm-2.1/ --enable-languages=c,c++ --disable-shared The build of llvm seems to

Hi, I've figured out a little more. #if defined DBX_DEBUGGING_INFO || XCOFF_DEBUGGING_INFO guards the declaration of type_queue, however, neither is defined on Intanium. In gt-dbxout.h type_queue's uses are unguarded and thus are undefined on Itanium. When I compared llvm-gcc's gt-dbxout.h with FSF gcc's, I found that type_queue was never used in FSF gcc's version. Does

sorry ! I have re-corrected the title. ------------------ 原始邮件 ------------------ 发件人: "Sheng Wang"<wansheg at gmail.com>; 发送时间: 2009年9月4日(星期五) 下午3:23 收件人: "LLVMdev"<LLVMdev at cs.uiuc.edu>; 主题: [LLVMdev] Dose I need to build llvm-gcc front-end from sourceresolve this error? /* mm.cpp */ #include<iostream> using namespace std; struct xx{ int x;

On 3/22/23 11:42, Laszlo Ersek wrote: > Now the "podman build -f ci/containers/alpine-edge.Dockerfile -t > libnbd-alpine-edge" command is failing with a different error message -- > the download completes, but the internal relinking etc fails due to > permission errors, which I don't understand. I've asked Martin for comments. > > Meanwhile, your other email (=

Hello, I’m trying the following thing: • build and install llvm with mgcc (system compiler) • build and install llvm-gcc with mgcc • build llvm with llvm-gcc • deinstall llvm(old), install llvm(new) • build llvm-gcc with llvm-gcc(old) • deinstall llvm-gcc(old), install llvm-gcc(new) However, I have the problem that the llvm-gcc(new) does not work: after it is compiled, it tries to build libgcc2