similar to: [ANNOUNCE] xf86-video-i128 1.4.1

This is a maintenance release of Number Nine Imagine 128 DDX. There was one patch that has been languishing over at Patchwork X.org website (https://patchwork.freedesktop.org/patch/122831/) for more than 2 years, so I decided to apply it, and release a new version. With that patch applied and one more small patch I authored, the DDX compiles cleanly without compilation warnings. Kevin Brace

Adam Jackson (3): Death to RCS tags. Fix distcheck i128 1.3.0 Alan Coopersmith (2): Replace references to XFree86/XF86Config in man page renamed: .cvsignore -> .gitignore Brice Goglin (1): Define I128_*_VERSION* using PACKAGE_VERSION_* Dave Airlie (3): i128: pciaccess conversion i128: drop ansi C wrapper i128: fixup typo Matthieu Herrb

Last-minute fix for 7.4. Adam Jackson (1): Don't store pScrn->monitor->DDC manually, let xf86SetDDCproperties do it. Julien Cristau (1): Bump to 1.3.1 Paulo Cesar Pereira de Andrade (2): Compile warning fixes. Replace calls to xf86usleep with calls to usleep and include unistd.h. git tag: xf86-video-i128-1.3.1

xf86-video-dummy - virtual/offscreen frame buffer driver for the Xorg X server ------------------------------------------------------------------------------ Alan Coopersmith (4): Avoid leaking pixel memory if DUMMYScreenInit fails gitlab CI: stop requiring Signed-off-by in commits List argument types in dummyRec->CreateWindow() function declaration xf86-video-dummy

A few cleanup patches that have been sitting on the branch for almost a year. The void driver is a dummy driver that does nothing and just fulfils the requirements of really old servers that must have an input device. It is just dead weight for any server released after 2007 or so. Don't use it. Alan Coopersmith (4): Link with $(XORG_LIBS) to support no-undefined linking Fix an

Adam Jackson (3): Death to RCS tags. Fix distcheck i128 1.2.0 Alan Coopersmith (2): Replace references to XFree86/XF86Config in man page renamed: .cvsignore -> .gitignore Brice Goglin (1): Define I740_*_VERSION* using PACKAGE_VERSION_* Dave Airlie (1): i740: pciaccess conversion Matthieu Herrb (1): Makefile.am: nuke RCS Id Paulo Cesar Pereira

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 It's a bit after 11pm, on the 11th day of the 11th month of the year, so what better time for a new release of X11! Release Candidate 1 of X11R7.6 has been posted at: http://www.x.org/releases/X11R7.6-RC1/ This includes all the source tar files for the versions of the modules currently considered part of the core release set (aka the

Compatibility release for inputproto 1.4. Alan Coopersmith (3): Replace references to XFree86/XF86Config in man page renamed: .cvsignore -> .gitignore Move from TSCalibrationCtl to AbsCalibCtl - requires inputproto >= 1.4.1 Brice Goglin (1): Define CITOUCH_VERSION* using PACKAGE_VERSION* Tilman Sauerbeck (3): Bumped version to 2.2.1. Added some more

xf86-input-elographics - Elographics input driver for the Xorg X server ----------------------------------------------------------------------- Alan Coopersmith (6): gitlab CI: ensure libtool is installed in build container configure: Use LT_INIT from libtool 2 instead of deprecated AC_PROG_LIBTOOL configure: clear up obsolete macro warnings from autoconf Move X.Org's

xf86-input-mouse is the Xorg server mouse driver for non-evdev OS'es. This release drops support for Xorg 1.6.x, and now requires Xorg 1.7 or later. On Solaris, it fixes a compatibility issue with the Xorg 1.13 ABI changes, allowing this driver to build for the upcoming Xorg 1.13 release. It also exposes "Device Node" (read-only), "Mouse Middle Button Emulation"

xwininfo prints information about windows on an X server. Various information is displayed depending on which options are selected. This release adds an option, disabled by default, to use libxcb-errors to improve the reporting of any X protocol error messages that may occur. To enable it, pass --with-xcb-errors to configure. Alan Coopersmith (8): gitlab CI: add a basic build test

On Fri, Sep 25, 2020 at 10:03 AM Wei Wang <weiwangcloud2020@gmail.com> wrote: > On Thu, Sep 24, 2020 at 2:58 PM Ján Tomko <jtomko@redhat.com> wrote: > >> On a Thursday in 2020, Wei Wang wrote: >> >Seems it didn't appear on the mailing list, resent it. >> > >> > Hi folks, >> > >> >I'm trying to build libvirt using meson

On Fri, Aug 19, 2011 at 1:59 PM, Craig Smith <craig at ni.com> wrote: > In both LLVM 2.9 and the current svn head, I get the following error when running llc > > % llc < fxp2.ll > LLVM ERROR: Cannot select: 0xa5302b0: glue = carry_false [ID=7] > > on this code: > > target triple = "i386-pc-linux-gnu" > > define i32 @fxpadd(i32 %cl) { > entry:

In both LLVM 2.9 and the current svn head, I get the following error when running llc % llc < fxp2.ll LLVM ERROR: Cannot select: 0xa5302b0: glue = carry_false [ID=7] on this code: target triple = "i386-pc-linux-gnu" define i32 @fxpadd(i32 %cl) { entry: %0 = zext i32 %cl to i128 %1 = zext i32 %cl to i128 %2 = add i128 %1, %0 br label %L1001510 L1001510:

Hi everyone! Here, I have a question and am curious about i128. I want to know how the LLVM handle i128, because many compiler backend doesn't support i128 directly. So I am very curious and want to how the llvm handle this situation? Besides i128, such as i256, i512, even i24? Thanks. Best Regards Wu Zhao -------------- next part -------------- An HTML attachment was scrubbed...

Hello, Andrew > Is the backend the best place to do this or should I attempt to make > llvm-gcc not generate i128 in the first place? It depends whether i128 is a native type for alpha, or not. If it's not - frontend should not generate it. If it's native type then it might be useful just to declare new regclass with virtual 'wide' registers consist of register pairs and

I am seeing i128 from llvm-gcc on Alpha.  I know the calling convention for them, they are split into two registers, but I don't know if that should be handled in the frontend or the backend.  I would just as soon do it in the backend, but I didn't see any support in the new calling convention work for automatically splitting an argument into multiple registers. Is the backend the best

Silences warning with gcc 8.2: nouveau_xv.c: In function ‘NVInitVideo’: nouveau_xv.c:2247:68: warning: passing argument 2 of ‘vlCreateAdaptorXvMC’ discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers] adaptorsXvMC[0] = vlCreateAdaptorXvMC(pScreen, textureAdaptor[0]->name); ~~~~~~~~~~~~~~~~~^~~~~~ In file included

I think it's returned in 4 registers: eax, edx, esi, edi. Can someone confirm? Evan On Feb 27, 2008, at 8:33 AM, gohman at apple.com wrote: > Hello, > > Does anyone know of any precedent for handling i128 in the > calling convention on x86-32? I'm trying to write a testcase > that returns an i128 value, and LLVM currently has only two > 32-bit GPRs designated for

Most probably you need to properly specify the calling convention the backend is using for calling the runtime functions. Or implement the stub for udivti3 that performs the necessary argument lifting. I guess there is no standard ABI document describing the intended calling convention here, so I'd just do what mingw64 does here and make everything here compatible. On Thu, Apr 26, 2018 at