similar to: [LLVMdev] Fixed with hex numbers with raw_ostream

On May 18, 2012, at 11:50 AM, Nick Kledzik <kledzik at apple.com> wrote: > I've been using the nifty: > DEBUG(errs() << "Here is the state of things:\n"); > style of optional logging, but ran into an issue where I want to dump a table of information. The problem is getting the columns to line up, since the raw_ostream methods write numbers as variable length.

On Aug 4, 2009, at 2:04 PM, Aaron Gray wrote: > >>How do output hex in DOUT's ? > > >Please don't use DOUT, please use: > > > > DEBUG(errs() << stuff); > > > >instead. > > Okay, I will modify my code. But how do I do hexadecimal output ? > raw_ostream has a write_hex method. O << "foo: "; O.write_hex(42); ...

2009/8/5 David Greene <dag at cray.com> > On Tuesday 04 August 2009 18:24, Chris Lattner wrote: > > > The big issue is things like this: > > > > DOUT << foo.getName() << "\n"; > > > > When -debug is disable and even when assertions are turned off, > > foo.getName() is still called. When you use: > > Yep, that's a

On Tue, Aug 4, 2009 at 5:05 PM, Aaron Gray<aaronngray.lists at googlemail.com> wrote: > So I can say > >     DEBUG( err().write_hex(address); err() << "\n"; ); > > And can I say :- > >     DEBUG( err().write_hex(address) << "\n"; ); > > does it associate like that ? Yes. You can also use format objects from llvm/Support/Format.h, as

>>How do output hex in DOUT's ? >Please don't use DOUT, please use: > > DEBUG(errs() << stuff); > >instead. Okay, I will modify my code. But how do I do hexadecimal output ? Aaron -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090804/6614cf39/attachment.html>

On Tuesday 04 August 2009 18:24, Chris Lattner wrote: > The big issue is things like this: > > DOUT << foo.getName() << "\n"; > > When -debug is disable and even when assertions are turned off, > foo.getName() is still called. When you use: Yep, that's a problem. > DEBUG(errs() << foo.getName() << "\n"); > > When

Hi, I've been playing around with the APFloat class lately and I came across behavior I was not expecting based on reading the implementation comments and I'm wondering if it's a bug or intentional. The behavior concerns converting an APFloat to a string and back again. In the implementation of ``APFloat::toString(...)`` you can specify ``FormatPrecision`` as 0. The method comments

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

Hi. I'm still having problems to login with Windows 2000 SP2 into my Samba PDC. The idealx howto says: "user and group rids must be given in hexadecimal in LDAP", however it also says: "However, the rids were written in decimal in LDAP. So at least 2.2.3-pre, Samba do not read them as hexadecimal anymore.". What's the case for 2.2.4? hex or dec? Alexander Skwar --

How do output hex in DOUT's ? Thanks, Aaron -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090804/5dbbd4f7/attachment.html>

On Aug 4, 2009, at 8:29 AM, Aaron Gray wrote: > How do output hex in DOUT's ? Please don't use DOUT, please use: DEBUG(errs() << stuff); instead. -Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090804/cda5fe94/attachment.html>

Hi, I am trying to print a hex value ( 4111999A for 9.1) for a corresponding floating point number. The routine convertToHexString in APFFloat class only prints in C99 Floating point hexagondecimal constant (eg 1.e00000p3). Without writing my own routine, how do I get to print the hexadecimal representation for a floating point value? Sirish -- Qualcomm Innovation Center, Inc is a member

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

Hi @ll, targetting i386, LLVM/clang generates wrong code for the following functions: unsigned long __bswapsi2 (unsigned long ul) { return (((ul) & 0xff000000ul) >> 3 * 8) | (((ul) & 0x00ff0000ul) >> 8) | (((ul) & 0x0000ff00ul) << 8) | (((ul) & 0x000000fful) << 3 * 8); } unsigned long long __bswapdi2(unsigned long

When I compile llvm on my Linux box, it complains about missing STDOUT_FILENO in raw_ostream.cpp. The attached patch solves that problem. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: raw_ostream.cpp.diff URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20080822/401536e7/attachment.ksh>

Dear All, I am currently writing an analysis pass that uses a third-party library. I want to write a print() method for my pass (which takes one of the LLVM raw_ostream objects) and have it use a method from this third-party library to print out data. However, the third-party library uses std::ostream. Is there a way to create a std::ostream from a raw_ostream? -- John T.

I'm working on a patch for clang where diagnostics print out unprintable characters vi style. I'm looking for someone familiar with llvm's raw_ostream to review the portion that enables reversed colors. Thanks, Seth Begin forwarded message: > From: Eli Friedman <eli.friedman at gmail.com> > Subject: Re: [cfe-commits] r148389 - in /cfe/trunk:

This code from raw_ostream.h is really racy: raw_ostream &operator<<(StringRef Str) { // Inline fast path, particularly for strings with a known length. size_t Size = Str.size(); // Make sure we can use the fast path. if (Size > (size_t)(OutBufEnd - OutBufCur)) return write(Str.data(), Size); if (Size) { memcpy(OutBufCur, Str.data(), Size);

The high-level answer is that library code shouldn't hardcode output paths, including "-" and including using llvm::outs(). Library code should (in general) instead accept an ostream in its API and write to wherever it is being asked to write. If this is followed, the only place in any program using llvm::outs() is code which is not part of a "library" -- i.e. it is the

Shankar, What is the other output going to stdout? Seems like it could get mixed into the yaml output, causing problems. If -o is not supplied, the linker normally writes to a file called “a.out”. If this is for the core linker when running test suites, may would should have the core linker create a temp file or string buffer to write to (if -o not supplied) and then at the end read from