search for: hexadecimal

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

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...) > > Is there any code available in LLVM  to handle this kind of "standard float to LLVM float" conversion? If you're writing C++ code, just stick your float into an APFloat and doesn't worry about the hexadecimal coding. If you're generating textual IR, and...

...n 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...) >> >> Is there any code available in LLVM to handle this kind of "standard float to LLVM float" conversion? > > If you're writing C++ code, just stick your float into an APFloat and > doesn't worry about the hexadecimal coding. If you're gen...

...iced 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 http://llvm.org/ docs/LangRef.html#simpleconstants still says "Floating point constants use standard decimal notation (e.g. 123.421), exponential notation (e.g. 1.23421e+2), or a more precise hexadecimal notation (see below)". I...

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...

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 = "i386-apple-darwin9.5" @mydouble = constant doubl...

>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 when a...

On 01/05/2007 7:21 AM, Stephan wrote: > Hi, > >> 0x10L > returns: int 0 > > I would expect: int 16? > This happens with all integer constants given by hexadecimal notation. > It's a bug? Certainly looks like one; I've cc'd this to the bug list (but won't be able to look into fixing it). Duncan Murdoch > > >> sessionInfo() > R version 2.5.0 (2007-04-23) > i386-pc-mingw32 > > locale: > LC_COLLATE=German_Germ...

Hi all, I have noticed incorrect parsing of very small hexadecimal numbers like "0x1.00000000d0000p-987". Such a hexadecimal representation can can be produced by sprintf() using the %a flag. The return value is incorrectly reported as 0 when coercing these numbers to double using as.double()/as.numeric(), as illustrated in the three examples below: as....

...e problem, however, is that using decimal numbers I can only produce 8 colors. It starts to recyle them after that (so, if possible values of my color column are 1,2,3,4,5,6,7,8,9,10,11, the values 1 and 9 both produce red, 2 and 10 produce black). However, I knew I could get more colors by using hexadecimal (tested with the legend) So, I carefully produced a csv file with hexadecimal values instead of decimal ones (eg. elements in the column are #ffffff, #ff0000) but if I use col=data$color it doesn't work, the entire plot is white. If I use these set of hexadecimal values in the legend, it work...

From: Brett Walker <brett.walker at geometry.com.au> When printing hexadecimal numbers to a fixed width, padded with leading zeros, and also having a leading '0x'; the resultant string can be shortened by up to two characters if any leading zero padding character required is. int hexnum = 0x00001234; printf("%08X", hexnum); // results in 00001234...

In short if suppose i have some expression as a=b+c-d*e, and with the help of LLVM pass i want to make a string like this:- "[Hexadecimal address of 'b'] [opcode of +] [Hexadecimal address of 'c'] [opcode of -] [Hexadecimal address of 'd'] [opcode of *] [Hexadecimal address of 'e']". Than how can i make it................ -- View this message in context: http://llvm.1065342.n5.nabble.com/Getti...

Hi there, could somebody help me to convert a decimal number into a hexadecimal number? I know that there is the function "sprintf", but the numbers I want to convert consist of 20 or more numbers. "Spintf" is not able to convert these big numbers. Thanks for any help. Antje [[alternative HTML version deleted]]

...et, I met a weird behaviour once I tried to use this marks in the RPDB : the packets where successfully marked, but it seemed that RPDB didn''t succed in matching them (for those who already know the answer, I only used marks above 9). After googling a while, I found that ip(8) only accepts hexadecimal numbers for "fwmark" statement. IMHO, I think that allowing only hexadecimal values in ip(8) while iptables(8) allows to either use decimal or hexadecimal value is quite inconsistent. I checked ip(8) sources, and here is the point : } else if (strcmp(*argv, "fwmark") ==...

...> 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 http://llvm.org/ > docs/LangRef.html#simpleconstants still says > > "Floating point constants use standard decimal notation (e.g. > 123.421), exponential notation (e.g. 1.23421e+2), or a more precise > hexadecimal notation...

...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...) >>> >>> Is there any code available in LLVM to handle this kind of "standard float to LLVM float" conversion? >> >> If you're writing C++ code, just stick your float into an APFloat and >> doesn't worry about the hexadecimal coding...

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: &...

Hi, The -dot-cfg option of opt will write a diagram of an analyzed function's CFG to DOT format. If you then open the DOT file, you will see that the BasicBlocks are uniquely identified with hexadecimal addresses. For example, an edge from one block to another may look like: Node0x10026b0:s0 -> Node0x1004c20; I've been trying to figure out where these hexadecimal addresses come from. I've been up and down the code but remain at a loss. I can see where GraphWriter.h is actually...

>>>>> Florent Angly <florent.angly at gmail.com> >>>>> on Tue, 20 Dec 2016 13:26:36 +0100 writes: > Hi all, > I have noticed incorrect parsing of very small hexadecimal numbers > like "0x1.00000000d0000p-987". Such a hexadecimal representation can > can be produced by sprintf() using the %a flag. The return value is > incorrectly reported as 0 when coercing these numbers to double using > as.double()/as.numeric(), as illustrat...