search for: bumps

Displaying 20 results from an estimated 3340 matches for "bumps".

Did you mean: dumps
2017 Mar 07
0
[ANNOUNCE] OpenChrome DDX Version 0.6 released
Hi everyone, Finally figured out how to use the X.Org automatic submission script after realizing that I had to change the script in order for OpenChrome DDX to build in the first place. OpenChrome DDX Version 0.6 has added the following new features. - First official support for CX700, VX700, and VX800 chipsets integrated TMDS transmitter (i.e., DVI support) - Initial support for Silicon
2020 Mar 25
6
Bumping the CMake requirement for libc++ and libc++abi
On 03/25/2020 06:20 AM, Louis Dionne wrote: > > >> On Mar 25, 2020, at 00:47, Tom Stellard <tstellar at redhat.com> wrote: >> >> On 03/24/2020 09:00 PM, Petr Hosek via llvm-dev wrote: >>> In October, there was a discussion about updating CMake to 3.15: http://lists.llvm.org/pipermail/llvm-dev/2019-October/136295.html. No decision was made, but maybe we
2018 Dec 19
4
New LLVM git repository conversion prototype
On Wed, Dec 19, 2018, 13:21 David Greene via llvm-dev < llvm-dev at lists.llvm.org wrote: > [ Consider all of this to be preferences, not anything close to an > objection. ] > > Tom Stellard via llvm-dev <llvm-dev at lists.llvm.org> writes: > > > There haven't been many more responses in the last few days, so can we > > try to come to some kind of
2020 Mar 25
3
Bumping the CMake requirement for libc++ and libc++abi
On 03/24/2020 09:00 PM, Petr Hosek via llvm-dev wrote: > In October, there was a discussion about updating CMake to 3.15: http://lists.llvm.org/pipermail/llvm-dev/2019-October/136295.html. No decision was made, but maybe we should revisit that proposal? If we're going to require a newer version of CMake for some subprojects, I'd prefer to bump the minimum CMake version for all of LLVM.
2020 Mar 25
3
Bumping the CMake requirement for libc++ and libc++abi
> On Mar 25, 2020, at 13:07, Nikita Popov <nikita.ppv at gmail.com> wrote: > > On Wed, Mar 25, 2020 at 5:01 PM Tom Stellard via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: > On 03/25/2020 06:20 AM, Louis Dionne wrote: > > > > > >> On Mar 25, 2020, at 00:47, Tom Stellard <tstellar at redhat.com
2020 Mar 26
2
Bumping the CMake requirement for libc++ and libc++abi
> On Mar 25, 2020, at 19:42, Chris Tetreault <ctetreau at quicinc.com> wrote: > > I would like to just chime in and say that I’m fairly strongly opposed to any blanket version increases without justification. Having a low version requirement is a feature. It means that more people can build the codebase. We should increase the minimum CMake version requirement only if we need to do
2020 Mar 25
3
Bumping the CMake requirement for libc++ and libc++abi
Hi, The minimum CMake version currently advertised for libc++ and libc++abi is currently 3.4.3. I think the oldest version of CMake actually being tested on any builder is 3.7.0, so advertising 3.4.3 is somewhat of a lie (I'm pretty sure we're using features that require a more recent version already). However, we do need to bump it to 3.8.0 at least because CMake 3.7 doesn't know
2018 Feb 13
0
[RFC] Should we bump the bitcode version in LLVM 6.0?
2018-02-08 17:34 GMT-08:00 Quentin Colombet via llvm-dev < llvm-dev at lists.llvm.org>: > Hi, > > TL;DR > r317488 changed the way fast math flags are laid out in the bitcode and > anyone compiling a pre-llvm-6.0 bitcode with llvm-6.0 will lose all the > optimizations guarded by isFast and a pre-llvm-6.0 compiler compiling a > llvm-6.0 bitcode will potentially generate
2020 Mar 26
4
Bumping the CMake requirement for libc++ and libc++abi
I understand organization restrictions and old operating systems (I use CentOS 7 myself), but I’ll note that the only requirement for running a new CMake is the ability to download and untar a tarball; in particular, you don’t require sudo. (I understand that there may be restrictions around running arbitrary executables downloaded from the internet, which of course make sense, but I wanted to
2019 Aug 26
2
[nbdkit PATCH] filters: Bump API version
...b0ce4411/cb309687/df0cc21d (bumping to API version 2 for the combined changes between v1.2 and v1.4), but failed to do so for f184fdc3 (affecting v1.10), 4ca66f70 (affecting v1.12), or 5ee7bd29/ee61d232 (affecting the upcoming v1.14). So do it retroacively now, as well as backporting intermediate bumps to affected stable branches. Signed-off-by: Eric Blake <eblake@redhat.com> --- I'm pushing this soon. include/nbdkit-filter.h | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/include/nbdkit-filter.h b/include/nbdkit-filter.h index 94f17789..1ebd1cb6 100644 -...
2009 Apr 26
7
Bumps chart in R
Hi there, I would like to make a 'bumps chart' like the ones described e.g. here: http://junkcharts.typepad.com/junk_charts/bumps_chart/ Purpose: I'd like to plot the proportion of people in select countries living for less then one USD pr day in 1994 and 2004 respectively. I have already constructed a barplot - but I think a bu...
2018 Feb 09
9
[RFC] Should we bump the bitcode version in LLVM 6.0?
Hi, TL;DR r317488 changed the way fast math flags are laid out in the bitcode and anyone compiling a pre-llvm-6.0 bitcode with llvm-6.0 will lose all the optimizations guarded by isFast and a pre-llvm-6.0 compiler compiling a llvm-6.0 bitcode will potentially generate incorrect code w.r.t. fast math expectations. Should we bump the bitcode version because of that and have the autoupgrader
2019 Aug 27
0
Re: [nbdkit PATCH] filters: Bump API version
...f0cc21d (bumping > to API version 2 for the combined changes between v1.2 and v1.4), but > failed to do so for f184fdc3 (affecting v1.10), 4ca66f70 (affecting > v1.12), or 5ee7bd29/ee61d232 (affecting the upcoming v1.14). So do it > retroacively now, as well as backporting intermediate bumps to > affected stable branches. > > Signed-off-by: Eric Blake <eblake@redhat.com> > --- > > I'm pushing this soon. > > include/nbdkit-filter.h | 8 +++++--- > 1 file changed, 5 insertions(+), 3 deletions(-) > > diff --git a/include/nbdkit-filter.h b/in...
2018 Feb 13
2
[RFC] Should we bump the bitcode version in LLVM 6.0?
Hi Mehdi, > On Feb 13, 2018, at 12:34 PM, Mehdi AMINI <joker.eph at gmail.com> wrote: > > > > 2018-02-08 17:34 GMT-08:00 Quentin Colombet via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>>: > Hi, > > TL;DR > r317488 changed the way fast math flags are laid out in the bitcode and anyone compiling a pre-llvm-6.0 bitcode
2009 Oct 14
0
[ANNOUNCE] compiz-0.8.4
Compiz 0.8.4 is released! This is the second stable release of Compiz 0.8 series. This release brings two new plugins, translation updates, many bug fixes, improved stability, and better screen resolution change handling. Also included is additional integration work for KDE 4. In particular, window thumbnails are now supported in Plasma window tooltips with the new KDE compatibility plugin, the
2018 Feb 09
0
[RFC] Should we bump the bitcode version in LLVM 6.0?
Does the language reference need to be updated? http://llvm.org/docs/LangRef.html#fast-math-flags It still mentions "fast" On Thu, Feb 8, 2018 at 8:34 PM, Quentin Colombet via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi, > > TL;DR > r317488 changed the way fast math flags are laid out in the bitcode and > anyone compiling a pre-llvm-6.0 bitcode with
2018 Feb 09
0
[RFC] Should we bump the bitcode version in LLVM 6.0?
Just wanted to point out part of this even becoming a problem is the use of `isFast()`. There should be warnings against using isFast() and the existing code should be changed to query specific flags instead... - Matthias > On Feb 8, 2018, at 5:34 PM, Quentin Colombet via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi, > > TL;DR > r317488 changed the way fast math
2013 Dec 11
2
[syslinux:firmware] version: Bump version & Lua
Op 2013-12-11 om 02:09 schreef syslinux-bot for Matt Fleming: > Commit-ID: 5e59ac11d6d105591d6da742750ea2f804534d43 > Gitweb: http://www.syslinux.org/commit/5e59ac11d6d105591d6da742750ea2f804534d43 > Author: Matt Fleming <matt.fleming at intel.com> > AuthorDate: Wed, 11 Dec 2013 10:03:13 +0000 > Committer: Matt Fleming <matt.fleming at intel.com> >
2018 Feb 09
1
[RFC] Should we bump the bitcode version in LLVM 6.0?
Agree, but that wouldn’t solve the downgrade problem plus this is probably too late to fix LLVM 6.0 for all the isFast uses. > On Feb 9, 2018, at 10:05 AM, Matthias Braun <mbraun at apple.com> wrote: > > Just wanted to point out part of this even becoming a problem is the use of `isFast()`. > There should be warnings against using isFast() and the existing code should be
2014 May 18
2
OpenArena artifacts since version bump to 1.1.1
Hello! I'm using NVIDIA GeForce GT 640M. And beginning with this commit: commit 142c21b8d493318551932eee2e9d98ff14b473da Author: Christoph Bumiller <e0425955 at student.tuwien.ac.at> Date: Wed Mar 27 22:25:52 2013 +0100 drm/nouveau/drm: bump the driver version to 1.1.1 to report new features till the latest kernel 3.15-rc5 OpenArena game looks like this: