search for: support_

...ot overridden. This is from patch 1: > > + /* Does not look like a Nvidia device. */ > + if (!supports_mux && !supports_opt) > + return; > This is precisely what I'm saying, and I think it's wrong/strange. If you've detected that device A support_{X,Y}, you'll reset the support_{X,Y} flag anyway if device B is present... (continues further down) > The reason why later calls override early ones is because some Optimus > laptops have the _DSM method on both the Intel GPU (00:02.0) and the > Nvidia one (01:00.0). > I agree with...

Hi R-Community, I faced problems when building R 1.5.1 from sources on i686-linux-gnu (Mandrake Linux 8.2) _with gnome support_ After running configure: ./configure --with-x --x-includes=/usr/X11R6/include --x-libraries=/usr/X11R6/lib --with-gnome --with-gnome-includes=/usr/include/gnome-1.0 --with-gnome-libs=/usr/lib/gnome-libs --with-readline R is configured this way: --- R is now configured for i686-pc-linux-gnu So...

...: > > > > + /* Does not look like a Nvidia device. */ > > + if (!supports_mux && !supports_opt) > > + return; > > > This is precisely what I'm saying, and I think it's wrong/strange. If > you've detected that device A support_{X,Y}, you'll reset the > support_{X,Y} flag anyway if device B is present... (continues further > down) The flags will only be reset when device B supports at least one function. > > The reason why later calls override early ones is because some Optimus > > laptops have the...

...behavior that shall be provided by any function definition in the pro- gram. If a function defined in a C++ program fails to meet the required behavior when it executes, the behavior is undefined. 4 For non-reserved replacement and handler functions, Clause _lib.lan- guage.support_ specifies two behaviors for the functions in question: their required and default behavior. The default behavior describes a function definition provided by the implementation. The required behavior describes the semantics of a function definition provided by either th...

Hi Peter, On 24 May 2016 at 23:53, Peter Wu <peter at lekensteyn.nl> wrote: > Since "PCI: Add runtime PM support for PCIe ports", the parent PCIe port > can be runtime-suspended which disables power resources via ACPI. This > is incompatible with DSM, resulting in a GPU device which is still in D3 > and locks up the kernel on resume. > > Mirror the behavior of

(Hi Mike!) On May 1, 2008, at 6:11 PM, Mike Stump wrote: > On Apr 30, 2008, at 9:26 PM, Chris Lattner wrote: >> Personally to me, I have a bigger axe to grind with C++ operator new. >> AFAIK, the standard doesn't give leeway to do a number of interesting >> optimizations for new/delete because the user is explicitly allowed >> to >> override them and the std