search for: l281

...h `llc -code-model=large`. It produces: > > movslq (%rax,%rdi,4), %rsi > addq %rax, %rsi > jmpq *%rsi > Ah; I guess I actually should have spotted that. See https://github.com/llvm-mirror/llvm/blob/f79c57a412cf8ba35884c1d4e011e07baad334d9/lib/CodeGen/SelectionDAG/TargetLowering.cpp#L281 . I think you can just force it to use EK_BlockAddress for the large code model. > >> Second, is it okay to > >> silently fold into Reloc::PIC_ in this case and leave the user with > >> sporadic crashes? > > > > > > Large code model and PIC should be...

...it would rather be important to *keep* the symlink, and install to whereever the symlink is pointing, no ? > It could happen before creating the directory, e.g. here: > https://github.com/wch/r-source/blob/62f5acbdbdf36e1fc618510312125d1677d79941/src/library/tools/R/install.R#L277-L281 > One thing that was a bit surprising to me -- R does not remove a > pre-existing package installation if it exists (when installing from > source), it merely installs over it, so files / artifacts from a > previous package installation could be left over after installi...

...already existed at the 'instdir' path, and if it existed and was a symlink, R would remove that symlink before install. It could happen before creating the directory, e.g. here: https://github.com/wch/r-source/blob/62f5acbdbdf36e1fc618510312125d1677d79941/src/library/tools/R/install.R#L277-L281 One thing that was a bit surprising to me -- R does not remove a pre-existing package installation if it exists (when installing from source), it merely installs over it, so files / artifacts from a previous package installation could be left over after installing a new package. It seems this is n...

Eli Friedman wrote: > On Thu, Jul 28, 2016 at 6:13 PM, Ramkumar Ramachandra via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> We were just debugging a sporadic crash the other day, when we noticed >> that RIP-relative addressing was being used in a JumpTable, even when >> code and data were well over 4G apart. This is confusing, because we >> picked

When creating qcow2 images using virt-builder, is there a way to specify the qcow2 preallocation, as possible with qemu-img create -o preallocation=metada , for example? TIA, Y.

...g create -o > preallocation=metada , for example? No .. but .. it does default to preallocation=metadata provided that the output format is qcow2: https://github.com/libguestfs/libguestfs/blob/master/builder/builder.ml#L582-L585 https://github.com/libguestfs/libguestfs/blob/master/src/create.c#L281-L295 Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. h...

...g to 0x563faa6c6260"? If alias sets have been merged, you'll get the attached node forwarding to the root node; note the comment for `getForwardedTarget` making a reference to union-find: https://github.com/llvm/llvm-project/blob/release/10.x/llvm/include/llvm/Analysis/AliasSetTracker.h#L281 (with "merge" corresponding to the union-find collapsing for "union", https://en.wikipedia.org/wiki/Disjoint-set_data_structure#Union). You can see how `AliasSet::mergeSetIn` (called, e.g., by `AliasSetTracker::mergeAliasSetsForPointer`) sets up forwarding for `AS.Forward`:...

https://bugzilla.mindrot.org/show_bug.cgi?id=2517 Bug ID: 2517 Summary: GitHub version doesn't include ChangeLog Product: Portable OpenSSH Version: 6.8p1 Hardware: 68k OS: Mac OS X Status: NEW Severity: enhancement Priority: P5 Component: Documentation Assignee:

...inked directory would definitely be nice :-) I just thought the request might be out of scope. > > It could happen before creating the directory, e.g. here: > > > https://github.com/wch/r-source/blob/62f5acbdbdf36e1fc618510312125d1677d79941/src/library/tools/R/install.R#L277-L281 > > > One thing that was a bit surprising to me -- R does not remove a > > pre-existing package installation if it exists (when installing from > > source), it merely installs over it, so files / artifacts from a > > previous package installation could be...

...If alias sets have been merged, you'll get the attached node forwarding > to the root node; note the comment for `getForwardedTarget` making a > reference to union-find: > https://github.com/llvm/llvm-project/blob/release/10.x/llvm/include/llvm/Analysis/AliasSetTracker.h#L281 > (with "merge" corresponding to the union-find collapsing for "union", > https://en.wikipedia.org/wiki/Disjoint-set_data_structure#Union). > > You can see how `AliasSet::mergeSetIn` (called, e.g., by > `AliasSetTracker::mergeAliasSetsForPointer`)...

Hey Matt, That's awesome. Thank you very much for all the information and clarification! Just a few follow up questions. Could you kindly shed some lights on it? Thank you! 1. I tried to tweak the code in the following way: - Clang [-> LLVM-IR]: https://llvm.godbolt.org/z/n9rGrs - [LLVM-IR ->] opt: https://llvm.godbolt.org/z/Uc6h5Y And i note that the outputs are: Alias sets for