search for: unambig

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

...; as.Date("2001/1/1") >> Works fine >> as.Date("1/1/2001") >> Prints "1-01-20" ??? >> as.Date("13/1/2001") >> Prints "13-01-20" ??? >> >> as.Date("1/13/2001") >> Prints error: not in standard unambigous format >> It seems that as if both "1/1/2001" and "13/1/2001" were considered by R >> to b >> e in a standard unambiguous format (or otherwise an error be reported?) >> and yet they >> >> >> are parsed incorrectly according to what on...

# 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

...s messy (and there's a real bug lurking that this exposes). I think I want (actually I want octal because I was raised PDP-11, but not trying to rock that boat): ABCD\{LF}EFG\[89]\\ or similar for printf("ABCD\nEFG%c\\", 0x89). The point is to be - compact for mostly ascii - unambigous - guaranteed printable only - otherwise as simple as possible How would people feel about adjusting upsdebug_ascii to do this? I would consider a PR if it is ok, and skip the effort if not.

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

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

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 entirely possible for the human readab...

...inder alignment is already fulfilled. Adjusting the image size to protect the backup GPT will therefore cause new padding of one cylinder size. One could check whether the last 33*512 bytes of the ISO filesystem are occupied by a backup GPT. There are id texts and CRC-32 sums. So it would be quite unambigous. Nevertheless, this will stay guesswork and potentially risky for the content of the ISO filesystem. So i gave up the idea to unconditionally adjust filesystem size to image file size. It might neverthelss be a valuable option. E.g. --adjust_fs_size. Have a nice day :) Thomas

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? >> > > I can't construct one out of thin air, but i believe someone cited one to > you on the gdb mailing list. It...

...seconds. Leap Seconds are announced officially by the IERS http://www.iers.org/iers/products/eop/leap.html RFC2822 explicitly refers to "local time" and to UTC. Local (or civil) time is ALWAYS UTC (modulo some hours). UTC, expressed (as it should be) in hours minutes seconds format, is unambigous. So, if you want to be consistent with rfc2822, use local time or UTC. I don't think you need the rigor of TAI, and, if you use TAI, your internal clock time will be 20+ seconds off from the time on people's watches, which is likely to cause trouble. Regards Marshall Eubanks > ulti...

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

...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 to go back from LLVM IR to Clang AST (I've already encountered this problem). I wonder if abi::__cxa_demangle guarantees unambigous names? If so, then I can just replace current incorrect names that Clang generates, with names from demangler. In this case I don't even need to patch gdb, it will work as is. -Roman 2018-03-05 10:46 GMT-08:00 Daniel Berlin <dberlin at dberlin.org>: > > > On Mon, Mar 5, 20...

...need to go back from LLVM IR to Clang AST (I've already > encountered this problem). > I don't understand these use cases well enough to help, but if you think it's a serious issue, again, i'd take it up with the DWARF folks. > I wonder if abi::__cxa_demangle guarantees unambigous names? > No, it does not. > If so, then I can just replace current incorrect names that Clang > generates, with names from demangler. In this case I don't even need to > patch gdb, it will work as is. > > -Roman > > 2018-03-05 10:46 GMT-08:00 Daniel Berlin <dber...

...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 <- "2009-02-29" # Note: 2009 not a leap year > as.Date(date1) Error in fromchar(x) : character string is not in a standard unambiguous format As I have many instances of date entries like this, date1, date2, date3, etc. , I'd like the script to error out gracefully and to be able to point the user to which date they need to correct, rather than "Error in fromchar(x)...", which doesn't make it obvious what th...

...g that this exposes). > > I think I want (actually I want octal because I was raised PDP-11, but > not trying to rock that boat): > > ABCD\{LF}EFG\[89]\\ > > or similar for printf("ABCD\nEFG%c\\", 0x89). The point is to be > - compact for mostly ascii > - unambigous > - guaranteed printable only > - otherwise as simple as possible > > How would people feel about adjusting upsdebug_ascii to do this? I > would consider a PR if it is ok, and skip the effort if not. > > > > _______________________________________________ > Nut...

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

...ang AST (I've already >> encountered this problem). >> > > I don't understand these use cases well enough to help, but if you think > it's a serious issue, again, i'd take it up with the DWARF folks. > > >> I wonder if abi::__cxa_demangle guarantees unambigous names? >> > > No, it does not. > > >> If so, then I can just replace current incorrect names that Clang >> generates, with names from demangler. In this case I don't even need to >> patch gdb, it will work as is. >> >> -Roman >> >>...

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 <