similar to: [LLVMdev] Odd problem with command line options

> I'm linking a program (my ellsif driver) that basically brings in most > of the LLVM stuff: bitcode reading, optimizations, linking, and target > code generation. > > All of a sudden, I'm getting the following when I run: > [~/elsa/ellsif] dev% ./ellsif -v test/ofmt.i test/sieve.i -time-actions > -O5 > <premain>: CommandLine Error: Argument

Jay Foad wrote: >> I'm linking a program (my ellsif driver) that basically brings in most >> of the LLVM stuff: bitcode reading, optimizations, linking, and target >> code generation. >> >> All of a sudden, I'm getting the following when I run: >> [~/elsa/ellsif] dev% ./ellsif -v test/ofmt.i test/sieve.i -time-actions >> -O5 >>

I'm linking a program (my ellsif driver) that basically brings in most of the LLVM stuff: bitcode reading, optimizations, linking, and target code generation. All of a sudden, I'm getting the following when I run: [~/elsa/ellsif] dev% ./ellsif -v test/ofmt.i test/sieve.i -time-actions -O5 <premain>: CommandLine Error: Argument 'machine-licm' defined more than once!

Hi all, I was trying to implement an obfuscation tool for C-code on the basis of LLVM. I got a prototype of the simple obfuscation transformation which converting control flow graph to something like a state machine. I am not sure I will have time to work on extending further this tool with new transformations like opaque predicates and decided to put here source code I have by now with hope

Hi, I'm gonna try to give some feedback, but I have only been working with LLVM for a few days, so don't take what I'm saying without verifying :-) > BasicBlock *ProgSlicer::CloneBasicBlock(const BasicBlock *BB, > DenseMap<const Value*, Value*> &ValueMap, > const char *NameSuffix, Function *F) { > > BasicBlock

Hi all, I am trying to write a pass where i am creating a clone of a function (the only difference being, the new function returns void , instead of any value). I am creating a new Function Type with a void return type (rest being the same as original function), and using this i am creating a new function body. Then, i clone the body of the old function into new function, but when ever i

On Feb 27, 2009, at 1:47 AM, Jay Foad wrote: > Hi, > > I noticed this code in lib/Transforms/Scalar/InstructionCombining.cpp: > > cerr << "WARNING: While resolving call to function '" > << Callee->getName() << "' arguments were dropped!\n"; > > If you're using LLVM as a static compiler, this warning is a

On Feb 27, 2009, at 10:37 AM, Evan Cheng wrote: > > On Feb 27, 2009, at 1:47 AM, Jay Foad wrote: > >> Hi, >> >> I noticed this code in lib/Transforms/Scalar/ >> InstructionCombining.cpp: >> >> cerr << "WARNING: While resolving call to function '" >> << Callee->getName() << "' arguments

Hi, I noticed this code in lib/Transforms/Scalar/InstructionCombining.cpp: cerr << "WARNING: While resolving call to function '" << Callee->getName() << "' arguments were dropped!\n"; If you're using LLVM as a static compiler, this warning is a bit incongruous, because it's not formatted in the same way as warnings from

Hi, > 4) There will be 4 new function attributes: > sign_ext_from_i8, sign_ext_from_i16 > zero_ext_from_i8, zero_ext_from_i16 > These attributes will be placed on the function CALL node by front-end to > inform the backend about such promotions and enable optimization of > return value. This should be sufficient for direct and indirect call. > (syntax of

> We are investigating if the certificate got updated by UIUC administrators > since they manage the certificates. The certificate was listed as valid from June 9, 2008 so I guess the old one expired? Gr. Matthijs -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL:

On Dec 1, 2011, at 1:13 PM, David Blaikie wrote: >>> (there's also some legitimate unreachable code warnings I'd be happy >>> to fix as I find them, things like: >>> >>> --- a/lib/Support/CommandLine.cpp >>> +++ b/lib/Support/CommandLine.cpp >>> @@ -294,10 +294,7 @@ static inline bool ProvideOption(Option *Handler, >>>

On Thu, Dec 1, 2011 at 9:11 AM, Chris Lattner <clattner at apple.com> wrote: > > On Dec 1, 2011, at 12:08 AM, David Blaikie wrote: > >> On Wed, Nov 30, 2011 at 10:42 PM, Chris Lattner <clattner at apple.com> wrote: >>> On Nov 29, 2011, at 12:26 AM, David Blaikie wrote: >>>> For a bit of an experiment I've been trying to compile LLVM & Clang

Dear CentOS folk, I've been try to solve one issue with rsyslog on CentOS 6, but can't figure it out. I've searched through rsyslog documentation, and used Google but not found anything that matches my issue. I'm sending output of a program to rsyslog using "logger -t progname". I've got the following config snippet in /etc/rsyslog.d: $FileCreateMode 0644 if

Aaron Gray wrote: > On Sun, Mar 1, 2009 at 4:24 AM, Nick Lewycky <nicholas at mxc.ca > <mailto:nicholas at mxc.ca>> wrote: > > Please try this patch. I tried to copy exactly what libtool would do > on Cygwin by reading the libtool source. > > > Hi Nick, > > Working fine on Cygwin :) Great to hear! I've committed the fix in r65922.

On Dec 1, 2011, at 12:08 AM, David Blaikie wrote: > On Wed, Nov 30, 2011 at 10:42 PM, Chris Lattner <clattner at apple.com> wrote: >> On Nov 29, 2011, at 12:26 AM, David Blaikie wrote: >>> For a bit of an experiment I've been trying to compile LLVM & Clang >>> with -Weverything (disabling any errors that seem like more noise/less >>> interesting).

On Wed, Nov 30, 2011 at 10:42 PM, Chris Lattner <clattner at apple.com> wrote: > On Nov 29, 2011, at 12:26 AM, David Blaikie wrote: >> For a bit of an experiment I've been trying to compile LLVM & Clang >> with -Weverything (disabling any errors that seem like more noise/less >> interesting). One warning I've recently hit a few instances of is >>

On Sun, Mar 1, 2009 at 4:24 AM, Nick Lewycky <nicholas at mxc.ca> wrote: Please try this patch. I tried to copy exactly what libtool would do on Cygwin by reading the libtool source. Hi Nick, Working fine on Cygwin :) Aaron Nick Aaron Gray wrote: On Fri, Feb 27, 2009 at 4:50 PM, Aaron Gray <aaronngray.lists at googlemail.com <mailto:aaronngray.lists at

Hi all, I was looking at the Internalize patch, and decided to clean it up a bit. The attached patch makes two functional changes to the pass: 1. If both -internalize-public-api-file and -internalize-public-api-list options are given on the commandline, only -file was used. Now, all options are respected and the contents of the file merged with the items given with the -list option(s). I

> How about setting an error flag, and error message in the Module, then > let the caller know the Module is broken? I'm not sure what you mean by "broken". In the case of this "arguments were dropped" warning, the module just contains some code that will give undefined behaviour if it gets executed. It would be reasonable for an optimiser to turn that code into a