similar to: [LLVMdev] Regression in 3.4's register allocator?

Displaying 20 results from an estimated 2000 matches similar to: "[LLVMdev] Regression in 3.4's register allocator?"

2014 May 14
2
[LLVMdev] Regression in 3.4's register allocator?
I can confirm that this regression has been fixed in trunk. Should I report this as a bug in 3.4? On Thu, Apr 24, 2014 at 10:17 PM, Quentin Colombet <qcolombet at apple.com>wrote: > Hi Niklas, > > This works for me with trunk r207129. > > We did fix some register allocation issues recently, don’t know which > change fixes the issue though. > > Thanks, > -Quentin
2014 Jun 01
4
[LLVMdev] Regression in 3.4's register allocator?
I think we have located the revision which fixes this regression: r206094 (or commit 6bb00df in llvm-mirror on GitHub). I have attached a patch which can be applied to the current release_34 branch (tested against the release_34 branch in llvm-mirror). With this patch the attached reg-alloc-test.ll file doesn't fail with the "LLVM ERROR: ran out of registers during register
2014 Jun 16
2
[LLVMdev] Regression in 3.4's register allocator?
Yep, quite right, Evan. Any regalloc differences due to that patch are purely coincidence; -Jim > On Jun 16, 2014, at 10:13 AM, Evan Cheng <evan.cheng at apple.com> wrote: > > Hi Niklas, > > The attached patch has nothing to do with register allocation. r206094 changes how cpu auto-detection is done. I believe it's now the responsibility of the tools (e.g. llc) to
2014 Feb 10
2
[LLVMdev] Fwd: [windows) how to use weak references with llvm 3.4 and windows?
Hello, I'm generating C code (and the resulting obj files) using llvm 3.4 for both unix and windows. And I use the dreaded weak references, that, for windows, are not too widely supported. When I link my application on linux, I have no issue. But when I'm doing the same on windows using mingw I got a duplicate symbol error :
2014 Feb 11
2
[LLVMdev] Fwd: [windows) how to use weak references with llvm 3.4 and windows?
Thanks for your clear answer. Do you know what modifier should I use to declare such weak symbols in my llvm intermediate code? So that it can be compiled to the .o file with the weak attribute ? Le 10 févr. 2014 19:44, "Reid Kleckner" <rnk at google.com> a écrit : > COFF doesn't support the same kind of concept of 'weak' that ELF does. > This is the issue that
2014 Feb 12
2
[LLVMdev] Fwd: [windows) how to use weak references with llvm 3.4 and windows?
So instead of using linkagetypes.weak I should use externalweaklinkage ? Le 11 févr. 2014 18:29, "Reid Kleckner" <rnk at google.com> a écrit : > You'd have to use extern_weak linkage. Clang compiles the foo declaration > to: > $ clang -cc1 -emit-llvm -o - t.c | grep declare.*@foo > declare extern_weak i32 @foo(...) #1 > > > > On Tue, Feb 11, 2014 at
2011 Feb 04
2
All DomU failing SSLv3 handshake (curl, apt-get, wget, etc.) but OK on Dom0
Hi, First of all I''ve googled this subject a lot (several hours) but right now I''m simply stuck. All my 4 DomU fails SSL handshake: > niklas@stats:~$ curl -vI https://graph.facebook.com > * About to connect() to graph.facebook.com port 443 (#0) > * Trying 69.63.181.58... connected > * Connected to graph.facebook.com (69.63.181.58) port 443 (#0) > * successfully
2012 Sep 15
5
create new variable with ifelse? (reproducible example)
Dear R users, I have a reproducible data and try to create new variable "clo" is 1 if know variable is equal to "very well" or "fairly well" and getalong is 4 or 5 otherwise it is 0. rep_data<- read.table(header=TRUE, text=" id1 id2 know getalong 100000016_a1 100000016_a2 very well 4 100000035_a1 100000035_a2 fairly
2008 Sep 12
7
embedding wxruby?
Hello, is it possible to code a wxWidgets GUI in C++ and pass the whole wxApp or just single windows to embedded Ruby code? This would be very nice to provide a scriptable plugin system. Greetings, Niklas _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users
2017 May 17
3
Improving packets/sec and data rate - v1.0.24
Niklas - Thanks! Yeah, your Github issue was very useful for me to understand what is probably causing our issue (the syscall chain done on every UDP packet). Very interesting that you're able to see around 90% of a Gig line on bare metal. Were you ever able to make any further progress on adjusting Tinc based on the investigation in https://github.com/gsliepen/tinc/issues/110 ? Martin -
2005 Oct 31
2
3phase progress?
Hi all! I've been (very) out of the loop for a while, up to the point that I had completely missed that the mailing list has moved. Oh well. However, Kjell Claesson poked at me regarding the 3phase stuff, so I found out that I had missed the recent events. In any case, it seems that the situation is unchanged regarding 3phase support. As some of you remember I made a suggestion for a
2011 Aug 12
8
Need some help with regular expression
I need to validate a string from a user (a location for use with geotagging) that is. I want to make sure that the user specify a city and a country in my inp ... So i wrote this => validates :usri_location, :presence => true, :format => {:with => /^[a-zA-Z]+{\,\s}+[a-zA-Z]/i}, :on => :create I want to make sure that the user writes city,
2017 Jan 27
4
Disallow binding via tinc
I'm looking for a way to add some (Linux) participants into my tinc network, but I want to protect them from accidentally binding a port so that it's accessible via tinc. For example, `nc -l` by default listens to all interfaces. Similarly, some software (I think mongodb < 2.6 was among those) bind to all interfaces AND allow unauthenticated access that can do remote code execution,
2013 Dec 07
8
Can't remove empty directory after kernel panic, no errors in dmesg
Hi List, so first the basics. I''m running Arch Linux with 3.13-rc2, btrfs-progs 0.20rc1.3-2 from the repo and I''m using a SSD. So I was having kernel panics with my USB 3.0 Gigabit card and was trying to get a panic output. These panics are intermittent and most often happen while using Chromium. Anyway so my system paniced while I was in Chromium. After the reboot Chromium
2017 Jan 27
1
Disallow binding via tinc
That would probably work, too; it's harder to configure though and easier to get wrong. If I could avoid having the tun0, that would trivially solve the problem. On 27/01/17 09:41, Azul wrote: > Why not just firewall incoming traffic on the clients? > > > On 27 Jan 2017 8:37 am, "Niklas Hambüchen" <mail at nh2.me > <mailto:mail at nh2.me>> wrote: >
2012 Nov 19
0
[LLVMdev] Debug information under windows
W dniu 2012-10-26 16:55, Daniel Kłobuszewski pisze: > Hello, > > Recently I found binaries produced with LLVM impossible to debug under > Windows. This was probably related to the following bug: > http://llvm.org/bugs/show_bug.cgi?id=13636 > > Asm generated from .ll files revealed that some offsets to debug > information were incorrect: they were absolute instead of
2009 Jul 09
3
Samba 3.4 on Centos 5.3
Dear Sirs, I'm running a vanilla CentOS 5.3 server, and yum there has Samba 3.0.33. What's the recommended way to install Samba 3.4 as an upgrade over 3.0.33? Just ./configure && make && sudo make install ? Cheers Nik
2016 May 27
2
asterisk odbc segfaults
after downgrade to 13.8.2 May 27 18:21:06 ast kernel: asterisk[16286]: segfault at 1010024 ip b49162cd sp bfac0940 error 4 in libmysqlclient.so.16.0.0[b48f1000+12e000] after downgrade to 13.7.2 asterisk is ok Dne 27.5.2016 v 18:09 Marek ?ervenka napsal(a): > btw info from my segfault > > Core was generated by `/usr/sbin/asterisk -f -vvvg -c'. > Program terminated with signal 11,
2016 May 29
2
asterisk odbc segfaults
doesnt work for me Dne 29.5.2016 v 17:48 Niklas Larsson napsal(a): > Hi, > > > On 2016-05-27 18:28, Marek ?ervenka wrote: >> after downgrade to 13.8.2 >> May 27 18:21:06 ast kernel: asterisk[16286]: segfault at 1010024 ip >> b49162cd sp bfac0940 error 4 in >> libmysqlclient.so.16.0.0[b48f1000+12e000] >> >> after downgrade to 13.7.2 >>
2014 Jun 09
2
[LLVMdev] Regression in 3.4's register allocator?
Hi Tom, On 9 Jun 2014, at 15:36, Tom Stellard <tom at stellard.net> wrote: > Unfortunately, it is too late to get this into 3.4.2. With the 3.5 > release coming soon, I wasn't planning on doing another 3.4 point > release. We are likely to keep the llvm 3.4 port in FreeBSD for a while after 3.5 is released. We've only removed the llvm 3.1 port a couple of months ago. A