search for: march

ARM subtarget features are determined by parsing the target tuple string TT. (ParseARMTriple(StringRef TT) in ARMMCTargetDesc.cpp) In llc, the -march setting overrides the architecture specified in -mtriple. So when you invoke: $ llc -march arm -mtriple armv7-none-linux ... ParseARMTriple() will see TT == "arm-none-linux" instead of "armv7-none-linux". As a result, the target features will be set generically. (Note that usi...

On Mar 2, 2012, at 12:04 AM, David Meyer <pdox at google.com> wrote: > ARM subtarget features are determined by parsing the target tuple string TT. (ParseARMTriple(StringRef TT) in ARMMCTargetDesc.cpp) > > In llc, the -march setting overrides the architecture specified in -mtriple. So when you invoke: > > $ llc -march arm -mtriple armv7-none-linux ... > > ParseARMTriple() will see TT == "arm-none-linux" instead of "armv7-none-linux". As a result, the target features will be set generic...

Why does GCC produce faster code using "-march=pentium2 -mtune=pentium4" on a Pentium 4 chip versus plain -march=pentium4? Try it... CPUTYPE=pentium2 CFLAGS+= -mtune=pentium4 COPTFLAGS+= -mtune=pentium4 -- BSD Podcasts @ http://bsdtalk.blogspot.com/

Hi On AArch64 (ARM 64-Bit Platform), I see there is an inconsistency in the values accepted by -march option between clang and llc. --- $ llc -march=aarch64 -mattr=help 2>&1 | grep error $ #No Error $ llc -march=armv8a -mattr=help 2>&1 | grep error llc: error: invalid target 'armv8a'. $ clang -march=armv8a -E - < /dev/null 2>&1 | grep error $ #No Error $ clang -...

It seems that -march=cpp is broken. the -march=cpp is very useful for people trying to understand the builder API. But, if the output of -march=cpp does not even compile, it obviously creates code that is broken, so defeats the object of helping people understand the builder API. Why isn't -march=cpp tested at...

...er exist : doveadm user siroco : field value uid 3002 gid 2000 home /var/spool/dovecot/mail/s/siroco mail maildir:~/Maildir:LAYOUT=fs postmap -vq siroco ldap:/etc/postfix/ldap_virtual_aliases.cf return siroco 2 questions : postfix search with siroco or with siroco at citoyens2015.marche.be ? postmap must return siroco or siroco at citoyen2015.marche.be ? And I don't know if I set for alias_maps, virtual_mailbox_maps, virtual_alias_maps ? My postconf alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases, ldap:/etc/postfix/ldap-citoyen.cf append_dot_mydomain =...

...er exist : doveadm user siroco : field value uid 3002 gid 2000 home /var/spool/dovecot/mail/s/siroco mail maildir:~/Maildir:LAYOUT=fs postmap -vq siroco ldap:/etc/postfix/ldap_virtual_aliases.cf return siroco 2 questions : postfix search with siroco or with siroco at citoyens2015.marche.be ? postmap must return siroco or siroco at citoyen2015.marche.be ? And I don't know if I set for alias_maps, virtual_mailbox_maps, virtual_alias_maps ? My postconf alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases, ldap:/etc/postfix/ldap-citoyen.cf append_dot_mydomain =...

-march for clang and -march for llc do different things unfortunately. -march for clang at least on x86 is the same as -mcpu in llc. Which is an artifact of gcc compatibility. ~Craig On Sat, Mar 23, 2019 at 1:40 PM Doerfert, Johannes via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Oh, my...

It is my actual target architecture ________________________________ From: Doerfert, Johannes <jdoerfert at anl.gov> Sent: Saturday, March 23, 2019 1:30 PM To: J S Cc: via llvm-dev Subject: Re: [llvm-dev] Generating object files more efficiently I copied "-march=XYZ" from your original email, you have to replace it with your actual target architecture or simply drop it. ________________________________ From: J S <mm92...

XLSolutions Corporation is proud to announce our March 2007 R/S: Fundamentals and Programming Techniques - in Princeton March 1-2, 2007 : http://www.xlsolutions-corp.com/Rfund.htm This two-day beginner to intermediate R/S-plus course focuses on a broad spectrum of topics, from reading raw data to a comparison of R and S. We will learn the essential...

...st adds a target feature 'crypto'. However later we might want to allow people to select which set of crypto extensions is added and we hit the same issue. (maybe you'd go with -mcrypto as an 'auto' and -mcrypto8.4-a etc, which is also ugly) The other option would be to allow -march without a base architecture. E.g. -march=armv8-a+crc -march=+crypto Or have them combine into some common set, which breaks existing behaviour: -march=armv8-a+crc -march=armv8.4-a+dsp -> -march=amv8-a+dsp+crc Which gets into a lot of issues around how you choose the set of features. Smalle...

..... .......... .......... .......... .......... .......... .......... .......... .......... .......... .......... .......... .......... .......... .......... .......... .......... ....... downloaded 437Kb * Installing *source* package 'fields' ... ** libs g77 -mieee-fp -fPIC -O2 -g -pipe -march=i386 -mcpu=i686 -c css.f -o css.o g77 -mieee-fp -fPIC -O2 -g -pipe -march=i386 -mcpu=i686 -c csstr.f -o csstr.o g77 -mieee-fp -fPIC -O2 -g -pipe -march=i386 -mcpu=i686 -c cvrf.f -o cvrf.o g77 -mieee-fp -fPIC -O2 -g -pipe -march=i386 -mcpu=i686 -c dchold.f -o dchold.o g77 -mieee-fp -fPIC -O2...

...appropriate Current Options Comparison -------------------------- | GCC | Clang | |-------------------------------| | ARM | AArch64 | ARM | AArch64 | |----------------------|-----|---------|-----|---------| | -march with '+<ext>' | Y | Y | Y | Y | | checks extensions | Y | N | N | N | | .arch with '+<ext>' | N | N | N | Y | | .arch_extension | Y | Y | Y | N | | .fpu | Y | N | Y | N...

...X86 has deprecated ‘-mcpu’ in favour of ‘-mtune’, and it uses ‘-mtune’ to mean that the scheduling, etc. should be biased in favour of more performant code for the processor identified by ‘-mtune’, but that the code is still 100% functional on all other processors in the family identified by ‘-march’. MIPS and ARM seem to have a very different notion of what they mean, and at the end of my examination of these options, I came to the conclusion that there is no common convention for usage and it all seems very haphazard. With the processor that I am targeting, the notion of tuning sched...

...re: creating ./config.status config.status: creating src/Makevars ** libs g++ -m32 -I/usr/include/R -DHAVE_PNG_H -DHAVE_FREETYPE -Iext/ftgl -I/usr/include/freetype2 -Iext -I/usr/local/include -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i686 -mtune=atom -fasynchronous-unwind-tables -fpic -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i686 -mtune=atom -fasynchronous-unwind-tables -c BBoxDeco.cpp -o BBoxDeco.o g++ -m32 -I/usr/include/R -DHAVE_PNG_H -DHAVE_FREETYPE -Ie...

Hi, I apologize if I am not asking on the right mailing list. I am using the llvm-gcc4.2 from MacPorts. https://trac.macports.org/browser/trunk/dports/lang/llvm-gcc42/Portfile llvm-gcc does not seem to accept the -march flag. This is the error, I got: cc1: error: unrecognized command line option "-march" The port developer asked me to find out if this is a known issue. -- Nichols A. Romero, Ph.D. Argonne Leadership Computing Facility Argonne, IL 60490 (630) 447-9793

...generation is controlled by the -target option which I don’t believe is under discussion here. James On 18 May 2016, at 13:17, Bruce Hoult <bruce at hoult.org<mailto:bruce at hoult.org>> wrote: Note that armv8a modifies the A32 and T32 instruction sets, and is therefore an important -march option for 32 bit code. Therefore armv8a can not be used to imply aarch64. For example: - IT predication instruction with more than a single controlled 16 bit instruction, or an instruction that modifies PC is deprecated. All old uses of IT work by default, but a control bit enables the OS to cau...

...rote: > The point here is, if you are not building for Android. > You will hit this patch with cmake configuration -DCOMPILER_RT_TEST_TRIPLE=aarch64-linux-gnu > > + elseif("${COMPILER_RT_TEST_TARGET_ARCH}" MATCHES "aarch64") > + test_target_arch(aarch64 "-march=aarch64") > > I don't see "-march=aarch64" is a valid flag on either LLVM or GCC. > Should we replace this with a flag which is valid for only aarch64 and works for both LLVM and GCC ? I think it should be -march=armv8-a > > If the compiler-rt build works for oth...

...ted ‘-mcpu’ in favour of ‘-mtune’, and it uses ‘-mtune’ to > mean that the scheduling, etc. should be biased in favour of more > performant code for the processor identified by ‘-mtune’, but that the > code is still 100% functional on all other processors in the family > identified by ‘-march’. > > > This is correct. > MIPS and ARM seem to have a very different notion of what they mean, and > at the end of my examination of these options, I came to the conclusion > that there is no common convention for usage and it all seems very > haphazard. > > > MIP...

> > -Most- targets use -march. > > -eric > Do you meat that in most cases -target is used along with -march instead of -target and -mcpu? -- Rail Shafigulin Software Engineer Esencia Technologies -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-...