similar to: [LLVMdev] Different Runtimes using clang-gcc and clang-opt-llc-gcc

Hi Suresh, > $ clang -O0 -c -flto foo.c > $ llc foo.o ^ llc defaults to -O2 > $ gcc foo.o.s Ciao, Duncan.

Dear all, I am doing few experiments to do understand optimization phase interactions. Here is a brief description of my experiements. 1. I picked the list of machine independent optimizations acting on llvm IR (those that are enabled at O3). 2. for each optimzation in the optimization-list a) Compiled the program using 'clang -c O0 -flto program.c' b) opt

On 19 June 2011 14:44, Suresh Purini <suresh.purini at gmail.com> wrote: >  I am doing few experiments to do understand optimization phase > interactions. Here is a brief description of my experiements. > > 1. I picked the list of machine independent optimizations acting on > llvm IR (those that are enabled at O3). > 2.  for each optimzation in the optimization-list >  

Devang, I meant as an end user. -Suresh On Thu, Jun 16, 2011 at 11:00 PM, Devang Patel <dpatel at apple.com> wrote: > Suresh, > > > On Jun 15, 2011, at 9:13 PM, Suresh Purini wrote: > >> Dear all, >> >> What is the default loop-unroll factor in llvm? How can we specify >> our own unroll-factor? > > Here "we" means end user or a

Thanks for the info Teresa, Regards M Suresh From: Teresa Johnson <tejohnson at google.com> Sent: Thursday, June 20, 2019 7:15 PM To: Mani, Suresh <Suresh.Mani at amd.com> Cc: Rui Ueyama <ruiu at google.com>; llvm-dev <llvm-dev at lists.llvm.org> Subject: Re: [llvm-dev] Expected behavior of lld during LTO for global symbols (Attr Internal/Common) [CAUTION: External

Hi Teresa, Can you please let me know if there is any update on this issue. Thanks M Suresh From: Teresa Johnson <tejohnson at google.com> Sent: Tuesday, June 11, 2019 7:23 PM To: Rui Ueyama <ruiu at google.com> Cc: Mani, Suresh <Suresh.Mani at amd.com>; llvm-dev <llvm-dev at lists.llvm.org> Subject: Re: [llvm-dev] Expected behavior of lld during LTO for global symbols

The direct cause of this issue is that, previously lld converted common symbols to defined symbols before passing input files to LTO, and after r360841 they are passed as common symbols to LTO. Making lld to work as before is easy, as we can convert common symbols to defined symbols as before. Here is a patch to do that, and I confirmed that that restores the original behavior for the reported

Hello, I am working on finding good optimization sequences for a given program (phase ordering problem). I have the following setup. 1) The source programs are translated into LLVM IR using -O0 + -scalarrepl. 2) Find an optimization sequence using some strategy which translates the IR generated in the previous step into another IR. 3) Apply llc -O2 and map the IR in to target assembly code.

Suresh, On Jun 15, 2011, at 9:13 PM, Suresh Purini wrote: > Dear all, > > What is the default loop-unroll factor in llvm? How can we specify > our own unroll-factor? Here "we" means end user or a compiler developer ? The threshold is 150, see LoopUnrollPass.cpp - Devang

Dear all, What is the default loop-unroll factor in llvm? How can we specify our own unroll-factor? -Suresh

Hello, When we invoke the loop-unroll pass, the compiler is crashing. From the earlier posts in the mailing-list and from the bug reports, it is a known problem. Is there some one working on this bug? -Suresh

Looks like this is indeed related to r360841. In C, there are distinctions between declarations, definitions and tentative definitions. Global variables declared with "extern" are declarations. Global variables that don't have "extern" and have initializers are definitions. If global variables have neither "extern" nor initializers, they are called tentative

Hello, How can I convert Fortran Programs to llvm IR? Can I use dragonegg to generate an llvm IR and then use rest of the llvm tool set as it is? -Suresh

Hi , I have an issue during LTO phase of llvm compiler which is as follows, File t3.c --------- #include <stdio.h> #include <stdlib.h> // A linked list node struct Node { int data; struct Node* next; struct Node* prev; }; struct Node* head; /* Given a reference (pointer to pointer) to the head of a list and an int, inserts a new node on the front of the list. */

On Jan 7, 2018 8:46 PM, "toddy wang" <wenwangtoddy at gmail.com> wrote: @Sean, here is my summary of several tools. Format: (ID,tool, input->output, timing, customization, questions) 1. llc, 1 bc -> 1 obj, back-end compile-time (code generation and machine-dependent optimizations), Difficult to customize pipeline, N/A 2. LLD: all bc files and obj files -> 1 binary

Dear all, Is there a command line argument which prints the order of application of various analysis/transformation passes on a program using clang? -Suresh

@Sean, here is my summary of several tools. Format: (ID,tool, input->output, timing, customization, questions) 1. llc, 1 bc -> 1 obj, back-end compile-time (code generation and machine-dependent optimizations), Difficult to customize pipeline, N/A 2. LLD: all bc files and obj files -> 1 binary (passing -flto to clang for *.bc file generation), back-end link-time optimizations and

Red Hat Enterprise Linux Server release 6.4 (Santiago) gcc version 4.4.7 20120313 (Red Hat 4.4.7-3) (GCC) We see the issue in all our Intel based Linux servers. Thanks Suresh On 21 April 2015 at 12:41, Jean-Marc Valin <jmvalin at jmvalin.ca> wrote: > Still can't reproduce. What OS and compiler version? > > Jean-Marc > > On 21/04/15 02:48 AM, Suresh Thiriveedi

No, I meant LLD, the LLVM linker. This option for LLD is relevant for exploring different pass pipelines for link time optimization. It is essentially equivalent to the -passes flag for 'opt'. Such a flag doesn't make much sense for 'llc' because llc mostly runs backend passes, which are much more difficult to construct custom pipelines for (backend passes are often required

Hi Suresh, thanks for reporting this! I thought I fixed this with 8d94d3c3b44c3a27a69b153cef9be4b8e481150e. Did you run before or after that commit? Cheers, Johannes On 5/15/20 7:17 AM, Mani, Suresh via llvm-dev wrote: > [AMD Public Use] > > Hi , > > Please ignore the earlier header of Internal and Official use only. > > Thanks > M Suresh > > From: llvm-dev