search for: update_

...i 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 arguments against making it Python 3 is: * There are many Mac OS X users and Mac OS X 10.8 comes with Python 2.7 pre-installed [0] but not Python 3. * Forcing scripts to use Python 3 (by doing so we can avoid som...

...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 <https://reviews.llvm.org/D42450> , the arguments against making it Python 3 is: > > * There are many Mac OS X users and Mac OS X 10.8 comes with Python 2.7 pre-installed [0] but not Python 3. > * Forcin...

...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 arguments against making it Python 3 is: > > * There are many Mac OS X users and Mac OS X 10.8 comes with Python 2.7 pre-installed [0] but not Python 3. > * Forcing scripts to use Python 3 (by doing so w...

...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 arguments > against making it Python 3 is: > > * There are many Mac OS X users and Mac OS X 10.8 comes with Python 2.7 > pre-installed [0] but not Python 3. > * Forcing scripts to use Python 3...

...t 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 arguments against making it Python 3 is: >> >> * There are many Mac OS X users and Mac OS X 10.8 comes with Python 2.7 pre-installed [0] but not Python 3. >> * Forcing scripts to use Python 3 (b...

...ang 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 <https://reviews.llvm.org/D42450> >> , the arguments against making it Python 3 is: >> >> * There are many Mac OS X users and Mac OS X 10.8 comes with >> Python 2.7...

> On Jan 31, 2018, at 10:04 AM, Fāng-ruì Sòng via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Thanks for the information. Then how about standalone scripts (many > one-file) like utils/update_check_tests.py that are unrelated to lit > or other important infrastructure? Can they be changed from > `#!/usr/bin/python2.7` to `#!/usr/bin/python3` shebang? > No. Every machine running macOS has /usr/bin/python and /usr/bin/python2.7 and because of system integrity protection it isn...

...ipts 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 arguments against >> making it Python 3 is: >> >> * There are many Mac OS X users and Mac OS X 10.8 comes with Python 2.7 >> pre-installed [0] but not Python 3. >> * Forcing...

Thanks for the information. Then how about standalone scripts (many one-file) like utils/update_check_tests.py that are unrelated to lit or other important infrastructure? Can they be changed from `#!/usr/bin/python2.7` to `#!/usr/bin/python3` shebang? On Tue, Jan 30, 2018 at 11:20 AM, Chris Matthews <chris.matthews at apple.com> wrote: > Personally, every machine I work with only ha...

...48 AM, Adrian Prantl <aprantl at apple.com> wrote: > > > >> On Jan 31, 2018, at 10:04 AM, Fāng-ruì Sòng via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> Thanks for the information. Then how about standalone scripts (many >> one-file) like utils/update_check_tests.py that are unrelated to lit >> or other important infrastructure? Can they be changed from >> `#!/usr/bin/python2.7` to `#!/usr/bin/python3` shebang? >> > > No. Every machine running macOS has /usr/bin/python and /usr/bin/python2.7 and because of system integri...

...e 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 arguments against >>> making it Python 3 is: >>> >>> * There are many Mac OS X users and Mac OS X 10.8 comes with Python 2.7 >>> pre-installed [0] but not Python 3...

Hi all, I''m happily using "HowToReuseEditViewsForNewViews" found at: http://wiki.rubyonrails.com/rails/pages/HowToReuseEditViewsForNewViews There''s this comment there saying you only need the tag "<%= auto_form %>" when using the code below. Can somebody tell me if that will work when extending it with model_name (some how)? I have several new_*

...;aprantl at apple.com> wrote: >> >> >> >>> On Jan 31, 2018, at 10:04 AM, Fāng-ruì Sòng via llvm-dev <llvm-dev at lists.llvm.org> wrote: >>> >>> Thanks for the information. Then how about standalone scripts (many >>> one-file) like utils/update_check_tests.py that are unrelated to lit >>> or other important infrastructure? Can they be changed from >>> `#!/usr/bin/python2.7` to `#!/usr/bin/python3` shebang? >>> >> >> No. Every machine running macOS has /usr/bin/python and /usr/bin/python2.7 and because...

...to be updated. IME, many of our tests check way too much. Codegen tests are particularly egregious in this regard because many are (re-)generated and match whole functions of asm. One of the major problems with using FileCheck regexps in generated tests is that it's very difficult to take an update_*_test_checks.py output and whittle it down because the FileCheck regexps define and use variables which need to be massaged while altering the test. I have some patches that help alleviate this. > This problem goes away if the test method by default ignored value > names/MDNode numbers and...

...gt; `#!/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 arguments > against > >>> making it Python 3 is: > >>> > >>> * There are many Mac OS X users and Mac OS X 10.8 comes with Python 2.7 > >>>...

...gt; `#!/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 arguments > against > >>> making it Python 3 is: > >>> > >>> * There are many Mac OS X users and Mac OS X 10.8 comes with Python 2.7 > >>>...

...>> `#!/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 <https://reviews.llvm.org/D42450> , the arguments against > >>> making it Python 3 is: > >>> > >>> * There are many Mac OS X users and Mac OS X 10.8 comes with...

The test as written is fragile because it requires a certain ordering. If the output order is not important, use CHECK-DAG rather than CHECK. This would be a failure to understand the testing tool. My experience, over a 40-year career, is that good software developers are generally not very good test-writers. These are different skills and good testing is frequently not taught. It’s easy to

Normally the FreeBSD Project tries very hard to avoid ABI breakage in "Stable Branches". However occasionally the fix for a bug can not be implemented without ABI breakage, and it is decided that the fix warrants the impact of the ABI breakage. We have one of those situations coming along for RELENG_7 (what will become FreeBSD 7.1). The ABI breakage should only impact kernel modules