similar to: Syntax for FileCheck numeric variables and expressions

Hi James, I like that suggestion very much but I think keeping the order of the two sides as initially proposed makes more sense. In printf/scanf the string is first because the primary use of these functions is to do I/O and so you first specify what you are going to output/input and then where to capture variables. The primary objective of FileCheck variables and expressions is to capture/print

To be clear, I do not intend to add support for hex specifier in the current patch, I just want to make sure the syntax we choose is going to allow it later. My immediate use case is decimal integer and I intend to write the code so that it's easy to extend to more type of numeric variables and expressions later. This way we'll only add specifier that are actually required by actual

Hi Alex, Thanks for the feedback. My first thought was that introducing the new pseudo var @EXPR is a nice way to generalize that syntax beyond @LINE since it would also evaluate to an arithmetic value. On the other hand there is a small inconsistency because @LINE evaluates to a value which can be part of an expression while @EXPR is an expression, and so the @ syntax as a whole becomes defined

Hi Alexander, Please forgive me if I'm missing the obvious but I do not see how the order helps allowing a comma in the expression. It seems to me that what would allow it is to make FMTSPEC mandatory or at least the comma to separate it (ie. [[#,EXPR]] for the default format specifier). In any case comma in a function-call like expression can be distinguished from comma for the format

Hi Alex, On Fri, 27 Jul 2018 at 11:53, Alexander Richardson <arichardson.kde at gmail.com> wrote: > > On Thu, 26 Jul 2018 at 10:28 Thomas Preudhomme <thomas.preudhomme at linaro.org> wrote: >> >> Hi Alexander, >> >> Please forgive me if I'm missing the obvious but I do not see how the >> order helps allowing a comma in the expression. It seems

I can certainly envision a use case for a [BASE + LENGTH + 4] computation to verify the address of a next-thingy. Comes up in DWARF dumps all the time. --paulr From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of James Henderson via llvm-dev Sent: Tuesday, July 31, 2018 11:53 AM To: Thomas Preudhomme Cc: llvm-dev Subject: Re: [llvm-dev] Syntax for FileCheck numeric variables

Hi James, Yes I think you summary proposal is a good one though I disagree with the colon being optional because there is ambiguity with looking for the value of VAR5 in the %x format. If anything, [[# %x, VAR5]] is equivalent to [[#:%x, VAR5]] or ([[#:%x = VAR5]] with your proposal. My other suggestion would be to use == rather than = since = could be confused with assignment. Note that

It appears to me based on my experiments with llvm-as that literal floating-point constants may be specified in the 64-bit IEEE hexadecimal format, but not in the 32-bit format. For instance, this file: target datalayout = "e-p:32:32:32-i1:8:8-i8:8:8-i16:16:16-i32:32:32- i64:32:64-f32:32:32-f64:32:64-v64:64:64-v128:128:128-a0:0:64- f80:128:128" target triple =

Hi, do you know, a method to convert an decimal value (integer) to the corresponding hexadecimal value ? thinks for help. Romain -- Lorrilli?re Romain UMR 8079 Laboratoire Ecologie, Syst?matique et Evolution B?t. 362 Universit? Paris-Sud 91405 Orsay cedex France tel : 01 69 15 56 85 fax : 01 69 15 56 96 mobile : 06 81 70 90 70 email : romain.lorrilliere at ese.u-psud.fr

>From the language guide: "The one non-intuitive notation for constants is the optional hexadecimal form of floating point constants. For example, the form 'double 0x432ff973cafa8000' is equivalent to (but harder to read than) 'double 4.5e+15'. The only time hexadecimal floating point constants are required (and the only time that they are generated by the disassembler) is

-- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones New in Fedora 11: Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 70 libraries supprt'd http://fedoraproject.org/wiki/MinGW http://www.annexia.org/fedora_mingw -------------- next part -------------- >From 712adf306e22487cf8ec4bf508917dbb8ed5f357 Mon Sep 17

Thanks very much for your answer. I?m trying the function ?strtoi? but it fails to convert character to numeric after the command "set[index] <- strtoi(set[index])". > strtoi(set[index]) ## This works: all values are numeric !!! [1] 1 2 3 4 2 8 9 7 > set[index] <- strtoi(set[index]) > print(set[10,1]) ## Problem: must be numeric !!!! [1] "1" Thanks

hi folks, this is driving me up the wall. Apologies for posting twice in the same week, I'm writing up a thesis. I wish to color-code some dots in an xy plot. I've got a csv file with various elements, one of which is the color-key (with the header 'color'). If the color-key is decimal (eg. 1,2,3) then I can use plot (X ~ Y, col=data$color) The problem, however, is that using

Le 2 juin 2010 à 12:21, Eli Friedman a écrit : > On Wed, Jun 2, 2010 at 2:59 AM, Stéphane Letz <letz at free.fr> wrote: >> Hi, >> >> We need to generate "Floating point constants" in our code. In http://llvm.org/docs/LangRef.html it is explained that FP has to follow special encoding rules to be handled by LLVM later one (hexadecimal coding...) >>

Hi, after upgrading to 2.1 I noticed that the format for floating point numbers in .ll files apparently changed. I now get errors like "llvm-as: var.ll:48,0: Floating point constant invalid for type" for such code: "@gmFloat = constant float 0.3". I checked with llvm-gcc and it now generates code for the hexadecimal floating point representation. The documentation at

On Jun 2, 2010, at 3:28 AMPDT, Stéphane Letz wrote: > > Le 2 juin 2010 à 12:21, Eli Friedman a écrit : > >> On Wed, Jun 2, 2010 at 2:59 AM, Stéphane Letz <letz at free.fr> wrote: >>> Hi, >>> >>> We need to generate "Floating point constants" in our code. In http://llvm.org/docs/LangRef.html it is explained that FP has to follow special

Hi Nelly, Are you trying to convert hexadecimal to decimal? nrdf Setting Value 1 Parameters a 2 Parameters b 3 Parameters c 4 Parameters d 5 Parameters e 6 Parameters 2 7 Parameters 8 8 Parameters 9 9 Parameters 7 10 1 a 11 2 b 12 3 c 13 4 d strtoi(nrdf$Value,16) [1] 10 11 12 13 14 2 8 9

Hi Dieter, Sorry my mistake. I wanted to convert them into Decimal (not Hexadecimal). Given this string, the desired answer follows: > ascii_str <- "ORQ>IK" 79 82 81 62 73 75 > ascii_str2 <- "FDC" 70 68 67 - Gundala Viswanath Jakarta - Indonesia On Mon, Dec 22, 2008 at 5:49 PM, Dieter Menne <dieter.menne at menne-biomed.de> wrote: > Gundala

On Thu, Aug 20, 2009 at 10:13 AM, Daniel Dunbar<daniel at zuster.org> wrote: > Fixed in r79450, along with an additional one of the same nature. > > Thanks, >  - Daniel Thanks Daniel and Enea for finding this! I'm adding a lot more test cases like this to APFloat's unittests so hopefully we won't have any other bugs lying around.

Hi, We need to generate "Floating point constants" in our code. In http://llvm.org/docs/LangRef.html it is explained that FP has to follow special encoding rules to be handled by LLVM later one (hexadecimal coding...) Is there any code available in LLVM to handle this kind of "standard float to LLVM float" conversion? Thanks. Stéphane Letz