search for: uproar

Displaying 20 results from an estimated 29 matches for "uproar".

2013 Jan 11
3
[LLVMdev] Obsolete PTX is NOT completely removed in 3.2 release
...rrored around the world now with cryptographic > hashes and signatures. Changing them will break things for many people, > especially for an extremely minor thing like an empty directory. > > I'm not sure if Pawel's tarball change should be reverted now as it > already caused uproar, so changing it back might only make matters worse. > The tarballs were changed? > > - Ben > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/ll...
2013 Jan 11
5
[LLVMdev] Obsolete PTX is NOT completely removed in 3.2 release
...e mirrored around the world now with cryptographic hashes and signatures. Changing them will break things for many people, especially for an extremely minor thing like an empty directory. > > > > I'm not sure if Pawel's tarball change should be reverted now as it already caused uproar, so changing it back might only make matters worse. > > > > The tarballs were changed? > > r172208 I finally updated the FreeBSD ports yesterday and today a user complained about distfile changes. IMO, this revision should be reverted or all the other BSDs will have to chase c...
2013 Jan 11
0
[LLVMdev] Obsolete PTX is NOT completely removed in 3.2 release
...t. They are mirrored around the world now with cryptographic hashes and signatures. Changing them will break things for many people, especially for an extremely minor thing like an empty directory. > > I'm not sure if Pawel's tarball change should be reverted now as it already caused uproar, so changing it back might only make matters worse. > > The tarballs were changed? r172208 - Ben
2013 Jan 11
0
[LLVMdev] Obsolete PTX is NOT completely removed in 3.2 release
...hic hashes and signatures. Changing them will >>> break things for many people, especially for an extremely >>> minor thing like an empty directory. >>> >>> I'm not sure if Pawel's tarball change should be reverted now >>> as it already caused uproar, so changing it back might only >>> make matters worse. >>> >>> The tarballs were changed? >> >> r172208 > > I finally updated the FreeBSD ports yesterday and today a user > complained about distfile changes. IMO, this revision should be > r...
2013 Jan 11
0
[LLVMdev] Obsolete PTX is NOT completely removed in 3.2 release
...this point. They are mirrored around the world now with cryptographic hashes and signatures. Changing them will break things for many people, especially for an extremely minor thing like an empty directory. I'm not sure if Pawel's tarball change should be reverted now as it already caused uproar, so changing it back might only make matters worse. - Ben
2013 Jan 11
2
[LLVMdev] Obsolete PTX is NOT completely removed in 3.2 release
...res. Changing them will > >>> break things for many people, especially for an extremely > >>> minor thing like an empty directory. > >>> > >>> I'm not sure if Pawel's tarball change should be reverted now > >>> as it already caused uproar, so changing it back might only > >>> make matters worse. > >>> > >>> The tarballs were changed? > >> > >> r172208 > > > > I finally updated the FreeBSD ports yesterday and today a user > > complained about distfile changes. I...
2013 Jan 11
6
[LLVMdev] Obsolete PTX is NOT completely removed in 3.2 release
.... Changing them will > >>> break things for many people, especially for an extremely > >>> minor thing like an empty directory. > >>> > >>> I'm not sure if Pawel's tarball change should be reverted now > >>> as it already caused uproar, so changing it back might only > >>> make matters worse. > >>> > >>> The tarballs were changed? > >> > >> r172208 > > > > I finally updated the FreeBSD ports yesterday and today a user > > complained about distfile change...
2013 Oct 27
0
[LLVMdev] [cfe-dev] RFC: A proposal to move toward using C++11 features in LLVM & Clang / bounding support for old host compilers
...ch too often makes very inconvenient > (or even impossible) to upgrade to newer VS versions. The latest example > that comes to mind was the release of VS2012: they removed Windows XP > support, as if upgrading the OS is a non-issue if you ask for it to your > users on a polite tone. An uproar followed and they backpedaled on a > service pack some months later, but that not always happens. I'm sorry, let me clarify. I'm saying that MSVC shouldn't be special from an LLVM policy perspective. We shouldn't have a general rule with an exception for MSVC: we should have a...
2013 Jan 11
4
[LLVMdev] Obsolete PTX is NOT completely removed in 3.2 release
Hi Pawel, PTX already be replaced with NVPTX. However, PTX subdirectory still sit in lib/Target in 3.2 release. Do you think update the release tarball is a good idea? Also could you remove it from the trunk? Thanks. Regards, chenwj -- Wei-Ren Chen (陳韋任) Computer Systems Lab, Institute of Information Science, Academia Sinica, Taiwan (R.O.C.) Tel:886-2-2788-3799 #1667 Homepage:
2013 Jan 11
0
[LLVMdev] Obsolete PTX is NOT completely removed in 3.2 release
...;>> Changing them will break things for many people, especially >>>>> for an extremely minor thing like an empty directory. >>>>> >>>>> I'm not sure if Pawel's tarball change should be reverted >>>>> now as it already caused uproar, so changing it back might >>>>> only make matters worse. >>>>> >>>>> The tarballs were changed? >>>> >>>> r172208 >>> >>> I finally updated the FreeBSD ports yesterday and today a user >>> complaine...
2013 Jan 13
3
[LLVMdev] Obsolete PTX is NOT completely removed in 3.2 release
...;>>> break things for many people, especially for an extremely >>>>>> minor thing like an empty directory. >>>>>> >>>>>> I'm not sure if Pawel's tarball change should be reverted now >>>>>> as it already caused uproar, so changing it back might only >>>>>> make matters worse. >>>>>> >>>>>> The tarballs were changed? >>>>> >>>>> r172208 >>>> >>>> I finally updated the FreeBSD ports yesterday and today a use...
2013 Jan 11
0
[LLVMdev] Obsolete PTX is NOT completely removed in 3.2 release
...hem will >>>>> break things for many people, especially for an extremely >>>>> minor thing like an empty directory. >>>>> >>>>> I'm not sure if Pawel's tarball change should be reverted now >>>>> as it already caused uproar, so changing it back might only >>>>> make matters worse. >>>>> >>>>> The tarballs were changed? >>>> >>>> r172208 >>> >>> I finally updated the FreeBSD ports yesterday and today a user >>> complained ab...
2013 Nov 09
5
[LLVMdev] [cfe-dev] RFC: A proposal to move toward using C++11 features in LLVM & Clang / bounding support for old host compilers
...es very inconvenient >> (or even impossible) to upgrade to newer VS versions. The latest example >> that comes to mind was the release of VS2012: they removed Windows XP >> support, as if upgrading the OS is a non-issue if you ask for it to your >> users on a polite tone. An uproar followed and they backpedaled on a >> service pack some months later, but that not always happens. > > I might be mistaken, but to compile for WinXP on VS 2012 you have to switch the Platform Toolset and AFAICT that means it will essentially be using the VS 2010 compiler and libraries....
2013 Jan 13
0
[LLVMdev] Obsolete PTX is NOT completely removed in 3.2 release
...;>> Changing them will break things for many people, especially >>>>> for an extremely minor thing like an empty directory. >>>>> >>>>> I'm not sure if Pawel's tarball change should be reverted >>>>> now as it already caused uproar, so changing it back might >>>>> only make matters worse. >>>>> >>>>> The tarballs were changed? >>>> >>>> r172208 >>> >>> I finally updated the FreeBSD ports yesterday and today a user >>> complaine...
2013 Jan 14
3
[LLVMdev] Obsolete PTX is NOT completely removed in 3.2 release
...hem will break things for many people, especially > >>>>> for an extremely minor thing like an empty directory. > >>>>> > >>>>> I'm not sure if Pawel's tarball change should be reverted > >>>>> now as it already caused uproar, so changing it back might > >>>>> only make matters worse. > >>>>> > >>>>> The tarballs were changed? > >>>> > >>>> r172208 > >>> > >>> I finally updated the FreeBSD ports yesterday and t...
2013 Jan 13
0
[LLVMdev] Obsolete PTX is NOT completely removed in 3.2 release
...eak things for many people, especially for an extremely >>>>>>> minor thing like an empty directory. >>>>>>> >>>>>>> I'm not sure if Pawel's tarball change should be reverted now >>>>>>> as it already caused uproar, so changing it back might only >>>>>>> make matters worse. >>>>>>> >>>>>>> The tarballs were changed? >>>>>> >>>>>> r172208 >>>>> >>>>> I finally updated the FreeBSD por...
2013 Oct 28
0
[LLVMdev] [cfe-dev] RFC: A proposal to move toward using C++11 features in LLVM & Clang / bounding support for old host compilers
...es very inconvenient >> (or even impossible) to upgrade to newer VS versions. The latest example >> that comes to mind was the release of VS2012: they removed Windows XP >> support, as if upgrading the OS is a non-issue if you ask for it to your >> users on a polite tone. An uproar followed and they backpedaled on a >> service pack some months later, but that not always happens. > I might be mistaken, but to compile for WinXP on VS 2012 you have to switch the Platform Toolset and AFAICT that means it will essentially be using the VS 2010 compiler and libraries. So wh...
2013 Oct 28
0
[LLVMdev] [cfe-dev] RFC: A proposal to move toward using C++11 features in LLVM & Clang / bounding support for old host compilers
...ch too often makes very inconvenient > (or even impossible) to upgrade to newer VS versions. The latest example > that comes to mind was the release of VS2012: they removed Windows XP > support, as if upgrading the OS is a non-issue if you ask for it to your > users on a polite tone. An uproar followed and they backpedaled on a > service pack some months later, but that not always happens. I might be mistaken, but to compile for WinXP on VS 2012 you have to switch the Platform Toolset and AFAICT that means it will essentially be using the VS 2010 compiler and libraries. So when it co...
2013 Oct 27
16
[LLVMdev] RFC: A proposal to move toward using C++11 features in LLVM & Clang / bounding support for old host compilers
(re-sending to the actual mailing lists... go go gadget typos!) On Sun, Oct 27, 2013 at 2:23 AM, Chandler Carruth <chandlerc at google.com>wrote: > Greetings, > > This has been discussed many times, and there are a lot of pro's and con's > on each side, but increasingly I think the project needs to draw a line in > the sand and put in place long-term policies around
2013 Jan 14
0
[LLVMdev] Obsolete PTX is NOT completely removed in 3.2 release
...eak things for many people, especially >>>>>>> for an extremely minor thing like an empty directory. >>>>>>> >>>>>>> I'm not sure if Pawel's tarball change should be reverted >>>>>>> now as it already caused uproar, so changing it back might >>>>>>> only make matters worse. >>>>>>> >>>>>>> The tarballs were changed? >>>>>> >>>>>> r172208 >>>>> >>>>> I finally updated the FreeBSD por...