Displaying 20 results from an estimated 900 matches similar to: "RFC: "REQUIRES: no*" considered harmful"
2016 May 23
0
SelectionDAGISel::Select's API considered harmful
Hans Wennborg <hans at chromium.org> writes:
> Can you put something in the release notes when this happens?
I already updated the release notes in r268693, when I added the void
Select option in the first place :)
> Thanks,
> Hans
>
> On Sat, May 21, 2016 at 10:57 AM, Justin Bogner via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
>> Update: All in tree
2018 Dec 09
0
"wbinfo -u" considered harmful towards Winbindd...
On Sun, 9 Dec 2018 20:20:00 +0100
Peter Eriksson via samba <samba at lists.samba.org> wrote:
> Our setup:
> Windows AD realm with ~115K users (and numerous groups etc)
> FreeBSD servers with Samba 4.7.6 and Samba 4.9.3 (both show the same
> growth)
>
> We just noticed that one of the ‘winbindd’ daemons on the servers
> seems to be growing and growing forever. A bit of
2016 May 21
0
SelectionDAGISel::Select's API considered harmful
Update: All in tree backends now implement `void Select`. I'll be
removing the SelectImpl path on Monday.
Justin Bogner <mail at justinbogner.com> writes:
> TLDR: Heads up for out of tree backends - you're going to need to update
> your *DAGToDAGISel::Select method to unconditionally replace nodes
> directly instead of returning the desired replacement.
>
> So I'm
2016 May 23
2
SelectionDAGISel::Select's API considered harmful
Can you put something in the release notes when this happens?
Thanks,
Hans
On Sat, May 21, 2016 at 10:57 AM, Justin Bogner via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> Update: All in tree backends now implement `void Select`. I'll be
> removing the SelectImpl path on Monday.
>
> Justin Bogner <mail at justinbogner.com> writes:
>> TLDR: Heads up for out of
2012 May 04
0
[LLVMdev] Extending GetElementPointer, or Premature Linearization Considered Harmful
Hi Preston,
On Fri, May 4, 2012 at 9:12 AM, Preston Briggs <preston.briggs at gmail.com> wrote:
>
> which produces
>
> %arrayidx24 = getelementptr inbounds [100 x [100 x i64]]* %A, i64
> %arrayidx21.sum, i64 %add1411, i64 %add
> store i64 0, i64* %arrayidx24, align 8
> {{{(5 + ((3 + %n) * %n)),+,(2 * %n * %n)}<%for.cond1.preheader>,+,(4 *
2016 May 05
2
SelectionDAGISel::Select's API considered harmful
TLDR: Heads up for out of tree backends - you're going to need to update
your *DAGToDAGISel::Select method to unconditionally replace nodes
directly instead of returning the desired replacement.
So I'm working on fixing the undefined behaviour I described in
llvm.org/PR26808. As part of this, we need to stop looking into deleted
SDNodes to check if they were, in fact, deleted. A big place
2010 Sep 23
2
rspec runner setting $KCODE considered harmful?
I ran across a problem today in which some code ran fine in regular
operation but failed in a test case. I scratched my head and thought "why
would running from within the test harness change the behavior of my code?"
Clearly it was the Heisenberg uncertainty principle in action! :)
I discovered the root cause was that the rspec runner is setting the magical
ruby global, $KCODE, to
2007 May 18
3
Fixtures considered harmful?
I''m trying to get really serious about doing true BDD for a new Rails
project, and I note that at <http://rspec.rubyforge.org/documentation/
rails/index.html> it says:
"we really don?t recommend the use of rails fixtures"
On the same page it also says (about Model specs):
"these are the only specs that we feel should actually interact with
the database"
2012 May 04
0
[LLVMdev] Extending GetElementPointer, or Premature Linearization Considered Harmful
Hi Preston,
>>> As noted in the GEP FAQ, GEPs don't support variable-length arrays;
>>
>> that's not quite right. The problem is only with arrays of variable length
>> arrays, and more generally with arrays where the element type has variable
>> size (this occurs with Ada, which has all kinds of funky variable sized types,
>> for example).
>
>
2011 Dec 03
3
Puppet considered harmful?
I am considering installing a Puppet agent on a legacy server running
an old, crappy, slow, leaky, yet important Java app. Nervous about
introducing anything that might (further) destabilize the app. What
are people''s experiences with Puppet in terms of resource usage (CPU/
memory/network/etc)? For starters will likely run it on the standard
daemon schedule. Ultimately may want to control
2013 May 02
2
BUG: virtio_mmio multi-queue competely broken -- virtio *registers* considered harmful
Virtiio_mmio attempts to mimic the layout of some control registers from
virtio_pci. These registers, in particular VIRTIO_MMIO_QUEUE_SEL and
VIRTIO_PCI_QUEUE_SEL,
are active in nature, and not just passive like a normal memory
location. Thus, the host side must react immediately upon write of
these registers to map some other registers (queue address, size, etc)
to queue-specific
2013 May 02
2
BUG: virtio_mmio multi-queue competely broken -- virtio *registers* considered harmful
Virtiio_mmio attempts to mimic the layout of some control registers from
virtio_pci. These registers, in particular VIRTIO_MMIO_QUEUE_SEL and
VIRTIO_PCI_QUEUE_SEL,
are active in nature, and not just passive like a normal memory
location. Thus, the host side must react immediately upon write of
these registers to map some other registers (queue address, size, etc)
to queue-specific
2003 Sep 25
7
[Bug 715] usage of BROKEN_SETREUID/BROKEN_SETREGID considered harmful
http://bugzilla.mindrot.org/show_bug.cgi?id=715
Summary: usage of BROKEN_SETREUID/BROKEN_SETREGID considered
harmful
Product: Portable OpenSSH
Version: -current
Platform: All
OS/Version: All
Status: NEW
Severity: major
Priority: P2
Component: Build system
AssignedTo:
2003 Apr 17
2
fontconfig-2.1.93 considered more harmful
There is an ongoing thread "fontconfig-2.1.92 considered harmful" on -CURRENT.
Because I have not moved to -CURRENT, I post this to -STABLE.
Since I upgraded to fontconfig-2.1.93 (on Apr 14) a lot of ports start to
complain a lot of "Cannot fork: Resource temporarily unavailable" errors.
What resource ? I inserted top into my ports build script to notice that
a lot of
2012 May 04
3
[LLVMdev] Extending GetElementPointer, or Premature Linearization Considered Harmful
Duncan Sands wrote:
>> As noted in the GEP FAQ, GEPs don't support variable-length arrays;
>
> that's not quite right. The problem is only with arrays of variable length
> arrays, and more generally with arrays where the element type has variable
> size (this occurs with Ada, which has all kinds of funky variable sized types,
> for example).
You're right, though
2001 Feb 06
4
argv[0] => host feature considered harmful
OpenSSH still has this feature, SSH-1.2.27 no longer has it. Admittedly it
can be useful sometimes, even though I'd prefer this to be done using a
trivial shell wrapper, which would be the UNIX way of doing things.
Not being able to call OpenSSH's ssh by another name (say ``ssh1'') can get in
the way when having to maintain two versions of ssh in parallel because the
``ssh ->
2010 Apr 01
4
POST-only logic in protect_from_forgery considered harmful?
Hi folks,
I am just getting into rails again after a multi-year stint of
mod_perl jobs, which might grant me some newbie-indemnity for the time
being - but I''ve found an issue I think warrants discussion.
As discussed here - http://api.rubyonrails.org/classes/ActionController/RequestForgeryProtection/ClassMethods.html
- the CSRF protection feature does not kick in for GET requests. This
2012 May 04
3
[LLVMdev] Extending GetElementPointer, or Premature Linearization Considered Harmful
Is there any chance of replacing/extending the GEP instruction?
As noted in the GEP FAQ, GEPs don't support variable-length arrays; when
the front ends have to support VLAs, they linearize the subscript
expressions, throwing away information. The FAQ suggests that folks
interested in writing an analysis that understands array indices (I'm
thinking of dependence analysis) should be
2008 Dec 02
3
A x86_64 processor can not run a x86_64 HVM
I own an Athlon 64 X2 Dual Core Processor 5200+. I enabled SVM extensions on BIOS. I did a power cycle.
xm dmesg shows me:
(XEN) AMD SVM: ASIDs enabled
(XEN) HVM: SVM enabled
I run a 64 bit Xen kernel (OpenSuse 11). Xen version is 3.2.1_16881_04-8.6
I _can not_ run any x86_64 O.S on a HVM domU, because it appears something like this: "your cpu does not support long mode. use a 32bit
2018 Dec 09
2
"wbinfo -u" considered harmful towards Winbindd...
Our setup:
Windows AD realm with ~115K users (and numerous groups etc)
FreeBSD servers with Samba 4.7.6 and Samba 4.9.3 (both show the same growth)
We just noticed that one of the ‘winbindd’ daemons on the servers seems to be growing and growing forever. A bit of detective work pointed us at the “wbinfo -u” command being that culprit. As part of a systems monitoring script we ran that once a