similar to: Python 2 compatibility for utility scripts

At the beginning of the year, I've landed a large set of patches to support both Python 2 and Python3 in most Python scripts. Looks like I missed some of them :-) At that time, backward portability with Python2 was still relevant, and I suspect it will still be the case for a few distributions that ship Python2 by default. That being said, Even RHEL8 uses Python3 by default, so at some point

IMO, having non-critical utility scripts require python 3 should be allowed now. But, not yet for any scripts which are critical to build or test the distributed components. If we need to spend some time to fix the test runner to allow properly skipping tests of python3-only components when python3 isn't available, that seems entirely worthwhile, since we only need to do that once. On Tue,

I define "critical" as: anything which is required to build or test any components which are part of a release. The intent being that we DO continue to support python 2 for building llvm, and for end-users of llvm, for now. However, developers of LLVM can be assumed to be able to install python3 if they want to be able to run these various optional, auxiliary, scripts. Having a unit

It sounds like you ran into a bug in the test infrastructure's code to determine if python3 is supported. Fixing that might be harder, but it only needs to be fixed once no matter how much more python3 development there will be. Right now, most of our scripts were originally written for python 2, so certainly it's easy for them to support python 2. But, it was a lot of work by various

On Tue, Jan 14, 2020 at 09:56:53PM +0000, Renato Golin via cfe-dev wrote: > GitHub PR is the "de facto standard", everyone knows, the entry cost > is practically zero. The UI is lean and missing features, but the > large availability of tooling (either targeting GitHub directly or > plain git) makes up for a lot of it. Just like with the "Everyone knows git", I

I define a pattern to move two 32bits gpr to 64bits fpr. like arm instructure fmdrr. But I need to use an even/odd register pair to save its 2 operands. I define in mytarget.td: myfmdrr: SDTypeProfile<1, 2, [SDTCisVT<0, f64>, SDTCisVT<1, i32>,     SDTCisSameAs<1, 2>]>; def my_fmdrr : ........... def myFMDRR : ....                       (outs FPR: $result), ins(GPR:

Hi LLVM-Devs, I noticed that many Python scripts under utils/ have a shebang of `#!/usr/bin/python` (which is a symlink to python2.7 on many platforms) and some of them use Python 2 syntax that is not compatible with Python 3 (e.g. print statements; str/bytes) I created a revision to migrate utils/update_{llc_,}_test_checks.py from Python 2 to Python 3 https://reviews.llvm.org/D42450 , the

hi, Dear Evan Cheng: My cpu is i32 embeded CPU. I define pseudo register pair registers. In mytargetRegisterInfo.td: def T0: RegisterWithSubRegs<"t0",[R0,R1]>; ... def GPR64 : RegisterClass<"mytarget", [i64], 64, [T0, T1.....] In mytargetISelLowering.cpp: I define i1, i8 , i16 and i32 are legal. 1. I still have problem. I save my function return double  value in

Hi Fangrui, for what it's worth regarding lldb, Zachary Turner has already done a lot of work to make the majority of its python code (most importantly, its testsuite) work with Python 3 as well as Python 2. J > On Jan 29, 2018, at 12:46 PM, Fāng-ruì Sòng via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi LLVM-Devs, > > I noticed that many Python scripts under

On Mon, 11 May 2015 14:42:36 -0600 Devin Reade wrote: > I just realized that more than MATE Terminal is affected. For > example, if I'm using firefox on a long web page, click the scrollbar > and quickly scroll through the page, then sometimes it behaves like > after a bit I've released the mouse button: Instead of scrolling, > the mouse (which is now outside of the scroll

+1 from my for changing LLVMs minimum requirements (for compiling llvm) to python3 and dropping python2 support. In case of lit we probably need to keep the code in a way that works with python 2 and 3 though as that will affect various projects outside of core llvm that started adopting it. - Matthias > On Jan 29, 2018, at 3:42 PM, Jason Molenda via llvm-dev <llvm-dev at

Hi Folks, A Grumble ... The message I just sent to R-help about "The hidden costs of GPL ..." has evoked a "Challenge" response: Hi, You??ve just sent a message to diagnosticando at uol.com.br In order to confirm the sent message, please click here This confirmation is necessary because diagnosticando at uol.com.br uses Antispam UOL, a service that avoids unwanted

On 2020-03-04, Louis Dionne via llvm-dev wrote: > > >> On Mar 4, 2020, at 12:13, Mehdi AMINI <joker.eph at gmail.com> wrote: >> >> >> >> On Wed, Mar 4, 2020 at 8:14 AM Louis Dionne <ldionne at apple.com <mailto:ldionne at apple.com>> wrote: >> Mehdi, Chris & others, >> >> I guess I did not express the main reasons for

On Feb 19, 2009, at 8:26 PM, 任坤 wrote: > hi, Dear Evan Cheng: > > My cpu is i32 embeded CPU. I define pseudo register pair registers. > > In mytargetRegisterInfo.td: > def T0: RegisterWithSubRegs<"t0",[R0,R1]>; > ... > def GPR64 : RegisterClass<"mytarget", [i64], 64, [T0, T1.....] > > In mytargetISelLowering.cpp: > I define i1, i8 ,

[ I am initially copying only a few lists since they seem like the most impacted projects and I didn't want to spam all the mailing lists. Please let me know if other lists should be included. ] I submitted D68230 for review but this is not about that patch per se. The patch allows update_cc_test_checks.py to process tests that should check target asm rather than LLVM IR. We use this

grumble, grumble, MS does not have llabs() llabs() is not defined in Visual Studio, however, _abs64() is. But if I switch to _abs64() the linker does not resolve __abs64(). I thought _abs64() was suppose to be in the CRT library. Any hints for a solution? c:\devwl\llvm\lib\CodeGen\SelectionDAG\DAGCombiner.cpp(295) : error C3861: 'llabs': identifier not found, even with argument-dependent

Personally, every machine I work with only has Python 2.7. Justin is correct that there is a non-trivial amount of effort to convert the bots. Python 3 is wonderful. But, a Python 3 dependency seems like one burden that could be avoided. We have already made that trade-off in the past, for example by only using standard python packages, so there is less/nothing to pip install when getting

On 03/09/15 19:42, Robert Moskowitz wrote: > > > On 09/03/2015 02:33 PM, Rowland Penny wrote: >> On 03/09/15 19:21, Robert Moskowitz wrote: >>> >>> >>> On 09/03/2015 02:17 PM, Rowland Penny wrote: >>>> On 03/09/15 19:05, Robert Moskowitz wrote: >>>>> >>>>> >>>>> On 09/03/2015 01:59 PM, Sketch wrote:

Hello list, when using Xen on our Bladecenter with the advanced management module everything works fine, but as soon as I switch the KVM to another blade and then switch back to xen machine, vga output is unavailable (due to wrong resolution or hz frequency? But it works if I don''t switch away). The machine itself works, only vga output is gone after switching kvm away from the box.

Hello all: I've been given the following data and have been asked to run a logit model using glm(). The variable, Y, is a proportion ranging from 0 to 1, X is a covariate. Without a base number of observations from which Y is computed as a proportion, I believe there is not sufficient information. If I try the model below, R seems to grumble with a complaint. glm(cbind(Y,1-Y) ~ X,