similar to: GSoC19: Improve LLVM binary utilities

(Adding just a bit to Jake's response) On Tue, Mar 26, 2019 at 11:31 AM Jake Ehrlich via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi Seiya, > > What should I prioritize? I suppose that improving llvm-objcopy is the >> most crucial work in this summer. > > > This is an opinion that will vary a lot from person to person. > +1! And don't forget that

> On May 23, 2019, at 2:05 AM, James Henderson via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > I discussed this with Seiya off the mailing list yesterday, and this was the suggestion we came up with, on the basis that GNU objcopy has support for the renaming for GDB support, but it might be confusing to people who are new to the system, so we provide a more expected output

Hi, I'm going to implement Mach-O support in llvm-objcopy. Before working on this, I'd like to hear your thoughts how llvm-objcopy should handle Mach-O section names. By convention, Mach-O section names are denoted by "<segment name>,<section name>". However, GNU objcopy renames them in the following rule [1]: - If the section name is well-known, rename it to an

Every case is different, but yes, as I said - I would like to take a closer look at the problem again, it might be the case that we don't need this complexity in this particular case, but want to double check. But yeah, in general I agree with you! On Thu, May 9, 2019 at 6:09 PM Jake Ehrlich <jakehehrlich at google.com> wrote: > I think that pretty much hits the nail on the head.

Dear all, My name is Mohamed and I am a first year computer science masters student. I am writing this email because I am interested in the project idea "Debug Info Should have no effect on codegen". So far I have built llvm and clang and I was trying to reproduce the problem on simple c++ programs but I can't. Being specific this are the steps I am doing: $ clang -g test.cc > $

Many llvm utilities use cl::ParseCommandLineOptions() (include/Support/CommandLine.h) to parse command line options. The cl library accepts both -long-option and --long-option forms, with the single dash form (-long-option) being more popular. We also have many binary utilities (llvm-objcopy llvm-objdump llvm-readobj llvm-size ...) whose names reflect what they imitate. For compatibility with GNU

> Are you proposing to make this the new style across all LLVM utilities? No. Only drop --long-option for GNU binutils replacements (people sometimes call them LLVM binary utilities): llvm-objcopy (D60439), llvm-ar, llvm-size, llvm-nm, etc. llvm-objdump (not sure what to do with mach-o specific dump options), llvm-readelf (not sure what to do with llvm-readobj) On Sat, Apr 20, 2019 at 2:13 AM

For binutil compatibility, and in general for any new tools, this sounds reasonable to me. But I'd worry that things like llvm-readobj have existed for a long time and people are used to flags like "-sections", and it may be complicated to change that now. (I guess this RFC is a check to see if this is true for anyone on the mailing list). What happens if you make this change and

It's actually a bit weirder than you might think. The CommandLine parser will happily eat as many dashes as you care to write, e.g., `----sections` is the same as `-sections`. On Tue, Apr 16, 2019 at 2:11 AM James Henderson via llvm-dev < llvm-dev at lists.llvm.org> wrote: > As I think I said elsewhere, I find it weird that LLVM tools accept long > arguments with a single dash,

Hi, I've tracked down what I believe is a bug in lld's relocation processing for R_X86_64_PC32 REL relocations. I'm producing the object file in a slightly unusual way: I'm using objcopy on a relocatable i386 ELF object file to convert it to x86_64 which transforms a R_386_PC32 into a R_X86_64_PC32. Steps to reproduce: 1. Assemble the attached bug.asm using nasm and note the

I tend to use the same tool-chain across various hosts so I made this very simple patch that allows you to pass the cross-compiler name to make ( e.g. make CROSS_COMPILE=i686-nptl-linux-gnu-). I'm not sure if patches should be attached or just pasted inline so I did both this time. BTW, it's relative to syslinux 4 but the same changes work with syslinux 3 although the patch won't

Hi, Thanks a lot for your answer. It seems lld is still the best solution, even if it does not work "right out of the box" for us today. We already have a solution for the "objcopy" part (added the required output format to llvm-objdump). The ScriptLayout class seems to be empty for now (on the master branch at least), but we do not need linker scripts today. All that is

Hi, On 03/20/2018 06:05 AM, Eric Christopher wrote: > > > On Fri, Mar 16, 2018 at 1:57 AM Paul Semel <semelpaul at gmail.com > <mailto:semelpaul at gmail.com>> wrote: > > Hi Eric, > > > On 03/15/2018 04:33 PM, Eric Christopher wrote: >> Hi Paul, >> >> >> >> I'm also interested in the command line

Hi Eric, On 03/15/2018 04:33 PM, Eric Christopher wrote: > Hi Paul, > > > >> I'm also interested in the command line replacements for GNU > Binutils : > >> > >> - What tools would you like to replace in priority ? > >> - Does this subject imply to add options/features to some of the > >> tools, or is it only

Hi, On 03/20/2018 03:06 PM, Paul Semel wrote: > Hi, > > On 03/20/2018 06:05 AM, Eric Christopher wrote: >> >> >> On Fri, Mar 16, 2018 at 1:57 AM Paul Semel <semelpaul at gmail.com >> <mailto:semelpaul at gmail.com>> wrote: >> >>     Hi Eric, >> >> >>     On 03/15/2018 04:33 PM, Eric Christopher wrote: >>>     Hi

On Fri, Mar 16, 2018 at 1:57 AM Paul Semel <semelpaul at gmail.com> wrote: > Hi Eric, > > On 03/15/2018 04:33 PM, Eric Christopher wrote: > > Hi Paul, > > >> >> I'm also interested in the command line replacements for GNU Binutils : >> >> >> >> - What tools would you like to replace in priority ? >> >> - Does this

Hi, I am still new to LLVM and also GNU softwares. I am doing a project using LLVM. I was building cfrontend on my windows cygwin, however I encountered this problem, may I now what is the cause? ******************************** my configuration output is: bash-2.05b$ ../src/configure --prefix=$CFEINSTALL --disable-threads --disable-n ls --disable-shared --enable-languages=c,c++ loading

On Fri, Jan 19, 2018 at 12:29 PM Leonardo Santagada <santagada at gmail.com> wrote: > Hi, > > No I didn't, I used cl.exe from the visual studio toolchain. What I'm > proposing is a tool for processing .obj files in COFF format, reading them > and generating the GHASH part. > > To make our build faster we use hundreds of unity build files (.cpp's with > a

One of the issues I reported in using lld as the FreeBSD base system linker is that the base system currently uses ld -r to convert a binary file (device firmware image) into an ELF object: > A tool for loading firmware into a wireless USB device includes a > built-in copy of the firmware image, and the image is converted to an > ELF file using ld -r. The invocation is: ld -b binary -d

On Fri, Jan 19, 2018 at 1:02 PM Leonardo Santagada <santagada at gmail.com> wrote: > On Fri, Jan 19, 2018 at 9:44 PM, Zachary Turner <zturner at google.com> > wrote: > >> >> >> On Fri, Jan 19, 2018 at 12:29 PM Leonardo Santagada <santagada at gmail.com> >> wrote: >> >>> Hi, >>> >>> No I didn't, I used cl.exe