search for: unambigously

...takes an i64 as parameter instead of a double* for my_struct. This parameter is then coerced into double* using an inttoptr instruction. The code in BasicAliasAnalysis.cpp which is triggered for x86 is the following: // Function arguments can't alias with things that are known to be // unambigously identified at the function level. if ((isa<Argument>(O1) && isIdentifiedFunctionLocal(O2)) || (isa<Argument>(O2) && isIdentifiedFunctionLocal(O1))) return NoAlias; isIdentifiedFunctionLocal(V) returns true for a noalias argument (such as result), but t...

Dear Brian, I dont understand what you mean. The thread was about the as.Date which you suggested to be used instead of the as.date. Following your advice I tried the as.Date and have questions about the observed behaviour, which was surprising to me. Is this what you call hijacking? Do you mean I ought start a new thread instead? I thought my question were relevant to the threads'

# HG changeset patch # Parent aa479945f718ff775c18afa2f37a391fca573114 # User carnold@suse.com # Date 1350668686 21600 pygrub: Add option to list grub entries The argument to "--entry" allows 2 syntaxes, either directly the entry number in menu.lst, or the whole string behind the "title" key word. This poses the following issue: From Dom0 there is no way to guess the number

I am looking at bestfortress and trying to figure out and fix some things, which is causing me to try to improve logging first. A few questions: 0) The developer guide doesn't seem to address any of this, or did I miss it? 1) It seems upsdebugx prints to stdout instead of syslog if in foreground. That's great but I didn't figure it out from docs. 2) I didn't find a plan for

...gt; > >> This parameter is then coerced into double* using an inttoptr >> instruction. The code in BasicAliasAnalysis.cpp which is triggered for x86 >> is the following: >> >> // Function arguments can't alias with things that are known to be >> // unambigously identified at the function level. >> if ((isa<Argument>(O1) && isIdentifiedFunctionLocal(O2)) || >> (isa<Argument>(O2) && isIdentifiedFunctionLocal(O1))) >> return NoAlias; >> >> isIdentifiedFunctionLocal(V) returns true fo...

> > I wonder if abi::__cxa_demangle guarantees unambigous names? >> > > No, it does not. > Interesting. Can you give an example of type where it fails? I'm currently working on hardware construction library for C++ (similar to Chisel (which is written in Scala)). And since C++ has no standardized reflection, I use DWARF as a source of reflection metadata. And in case of

On Tue, Mar 6, 2018 at 9:20 AM, Roman Popov <ripopov at gmail.com> wrote: > I wonder if abi::__cxa_demangle guarantees unambigous names? >>> >> >> No, it does not. >> > > Interesting. Can you give an example of type where it fails? > I can't construct one out of thin air, but i believe someone cited one to you on the gdb mailing list. It's

Hi, > There was a seventh patch. Yes. A late one because of more testing. Not only my --mbr, but also --mac and --uefi promised short options in their help text, but did not prepare the options string for getopt(3) to recognize these options. > It uses also reformatting. > Don't wait for me do it. If you explain to me what is necessary (and maybe also why), then i could try to do

On Tue, Mar 6, 2018 at 9:49 AM Daniel Berlin <dberlin at dberlin.org> wrote: > On Tue, Mar 6, 2018 at 9:20 AM, Roman Popov <ripopov at gmail.com> wrote: > >> I wonder if abi::__cxa_demangle guarantees unambigous names? >>>> >>> >>> No, it does not. >>> >> >> Interesting. Can you give an example of type where it fails?

>RFC822 is HISTORIC: please refer to RFC2822 instead. > >While UTC is sufficient for human beings, but not necessarily accurate >for machines, because of the leap year adjustment. TAI is the You mean leap seconds, not leap years. Since 1972, UTC == TAI modulo some number of seconds. Leap Seconds are announced officially by the IERS http://www.iers.org/iers/products/eop/leap.html

Op 2014-06-22 om 22:31 schreef Geert Stappers: > Op 2014-06-22 om 21:02 schreef Thomas Schmitt: > > > > following will be 6 patch proposals for isohybrid.c > > > > 1: Encode GPT partition names as UTF-16LE > > 2: Correct blocking factor in APM partition block counts > > 3: Correct end block address of first GPT partition > > 4: Write GPT backup to the

...coerced into double* using an inttoptr >>>> instruction. The code in BasicAliasAnalysis.cpp which is triggered for x86 >>>> is the following: >>>> >>>> // Function arguments can't alias with things that are known to be >>>> // unambigously identified at the function level. >>>> if ((isa<Argument>(O1) && isIdentifiedFunctionLocal(O2)) || >>>> (isa<Argument>(O2) && isIdentifiedFunctionLocal(O1))) >>>> return NoAlias; >>>> >>>> isId...

I don't understand how extra vtable ref DIE will help in case on non-polymorphic classes. If you remove virtual destructor from example, vtable won't be generated for class, but DWARF will still have incorrect ambiguous names for types. It will become a problem when you need to use debuginfo as a C++ runtime reflection (I've already seen this in a couple of projects). Or when you need

On Mon, Mar 5, 2018 at 11:55 PM, Roman Popov <ripopov at gmail.com> wrote: > I don't understand how extra vtable ref DIE will help in case on > non-polymorphic classes. If you remove virtual destructor from example, > vtable won't be generated for class, but DWARF will still have incorrect > ambiguous names for types. > 1. Calling them incorrect is ... not right. As

Hi All, I have an script in R which accepts user inputs for certain parameters, particularly dates, which the user inputs as character strings. eg: > date1 <- "2009-01-21" The script later parses the input via the as.Date function: > as.Date(date1) However, as.Date encounters an error when the string does not represent an actual date. eg: > date1 <-

Cheers, I don't think there is any particular strategy, at least not one I'd know of either :) So it is mostly ad-hoc, to keep smaller verbosity numbers reasonably quiet, and sufficient info to see the logic progression at a given debug level (e.g. if major milestones of a routine are logged at level N, further traces like "I saw value X here" would be N+1 or more). De-facto

Hi all, This may seem like a dumb question, but I work for an entity that is soon converting to XP across the board, and I will lose the ability to install software on my own. The entity has a policy of only using software that has been purchased and "properly licensed" (whatever that means). This means I will soon lose the ability to use R at work - something I can't do without

On Mon, Mar 5, 2018, 9:26 AM David Blaikie <dblaikie at gmail.com> wrote: > On Mon, Mar 5, 2018 at 9:09 AM Daniel Berlin <dberlin at dberlin.org> wrote: > >> On Mon, Mar 5, 2018 at 8:37 AM, David Blaikie <dblaikie at gmail.com> wrote: >> >>> >>> >>> On Sat, Mar 3, 2018 at 8:20 PM Daniel Berlin via llvm-dev < >>> llvm-dev

On Tue, Mar 6, 2018 at 8:39 AM Daniel Berlin <dberlin at dberlin.org> wrote: > On Mon, Mar 5, 2018 at 11:55 PM, Roman Popov <ripopov at gmail.com> wrote: > >> I don't understand how extra vtable ref DIE will help in case on >> non-polymorphic classes. If you remove virtual destructor from example, >> vtable won't be generated for class, but DWARF will

On Mon, Mar 5, 2018 at 9:09 AM Daniel Berlin <dberlin at dberlin.org> wrote: > On Mon, Mar 5, 2018 at 8:37 AM, David Blaikie <dblaikie at gmail.com> wrote: > >> >> >> On Sat, Mar 3, 2018 at 8:20 PM Daniel Berlin via llvm-dev < >> llvm-dev at lists.llvm.org> wrote: >> >>> On Fri, Mar 2, 2018 at 3:58 PM, Roman Popov via llvm-dev <