Displaying 20 results from an estimated 10000 matches similar to: "[LLVMdev] Inline assembly - multiple constraints and reloads."
2015 Feb 19
3
[LLVMdev] Patchpoints used for inline caches and pointless reloads
Hi All,
I am observing something i suspect is a misbehaviour of the register
allocator which impacts the performance of patchpoints. This occurs in
the context of an abstract machine which in some places uses inline
caches. The problematic code looks like this:
entry: ; Initialize the abstract machine
%db = call create_big_seldom_used_database()
; do a lot of things which increases register
2015 Mar 04
2
[LLVMdev] Inline Assembly: Memory constraints with offsets
> -----Original Message-----
> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu]
> On Behalf Of Krzysztof Parzyszek
> Sent: 03 March 2015 14:35
> To: llvmdev at cs.uiuc.edu
> Subject: Re: [LLVMdev] Inline Assembly: Memory constraints with offsets
>
> On 3/3/2015 6:01 AM, Daniel Sanders wrote:
> > Hi,
> >
> > I'm trying to
2015 Mar 03
5
[LLVMdev] Inline Assembly: Memory constraints with offsets
Hi,
I'm trying to implement the ZC inline assembly constraint for Mips. This constraint is a memory constraint that expands to an address with an offset (the range of the offset varies according to the subtarget), so the inline assembly in:
int data[10];
void ZC(void) {
asm volatile ("foo %0 %1" : : "ZC"(data[1]), "ZC"(data[2]));
}
Should expand to
2013 Jun 07
2
[LLVMdev] add Inline assembly in LLVM IR
Hi all,
I'm working for translating dex bytecode to LLVM IR
In order to communicate with Android interpreter,
The work have to add data below some instructions
I want to use inline assembly to add data.
Thus, I wrote a little program to find out the related LLVM IR
int main()
{
asm(".long 0x12345678");
return 0;
}
and I use clang to translate it into bitcode
It's the
2015 Mar 09
3
[LLVMdev] Inline Assembly: Memory constraints with offsets
> From: Krzysztof Parzyszek [kparzysz at codeaurora.org]
> On 3/4/2015 10:30 AM, Daniel Sanders wrote:
> >
> > Partial support for ZC is in my working copy at the moment. I've attached my WIP patches.
>
> Should have guessed that, ha.
>
> I've looked into this. My idea was to expand the single address operand
> of the inline-asm SDNode into two: base
2007 Apr 13
0
[949] branches/wxruby2/wxwidgets_282: Changes in Gauge API 2.6->2.8, remove comment cruft in header
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><meta http-equiv="content-type" content="text/html; charset=utf-8" /><style type="text/css"><!--
#msg dl { border: 1px #006 solid; background: #369; padding:
2007 Jul 20
0
[1124] trunk/wxruby2/samples/bigdemo/wxGauge.rbw: Use Wx::Timer instead of evt_idle to drive Gauge sample, to avoid 100%
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><meta http-equiv="content-type" content="text/html; charset=utf-8" /><style type="text/css"><!--
#msg dl { border: 1px #006 solid; background: #369; padding:
2010 May 18
2
Function that is giving me a headache- any help appreciated (automatic read )
note: whole function is below- I am sure I am doing something silly.
when I use it like USGS(input="precipitation") it is choking on the
precip.1 <- subset(DF, precipitation!="NA")
b <- ddply(precip.1$precipitation, .(precip.1$gauge_name), cumsum)
DF.precip <- precip.1
DF.precip$precipitation <- b$.data
part, but runs fine outside of the function:
days=7
2023 Jul 26
1
plotly
Colleagues,
Here is my reproducible code.
library(plotly)
t <- list(
? family = "Arial",
? size = 12,
? color = "black",
? face="bold")
t3 <- list(
? family = "Arial",
? size = 12,
? color = "black",
? face="bold")
t5 <- list(
? family = "Arial",
? size = 12,
? color = "black",
? face="bold")
2017 Mar 23
0
[Bug 1137] New: Element "flow tables" should not be syntactically unique...
https://bugzilla.netfilter.org/show_bug.cgi?id=1137
Bug ID: 1137
Summary: Element "flow tables" should not be syntactically
unique...
Product: nftables
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P5
Component:
2009 Oct 06
1
ggplot2 applying a function based on facet
Look at the bottom of the message for my question
#here is a little function that I wrote
USGS <- function(input="discharge", days=7){
library(chron)
library(gsubfn)
#021973269 is the Waynesboro Gauge on the Savannah River Proper (SRS)
#02102908 is the Flat Creek Gauge (ftbrfcms)
#02133500 is the Drowning Creek (ftbrbmcm)
#02341800 is the Upatoi Creek Near Columbus (ftbn)
#02342500 is
2007 Apr 26
0
[972] trunk/wxsugar/lib/wx_sugar/keyword_classes.rb: Fix missing keyword param for Wx::Gauge
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><meta http-equiv="content-type" content="text/html; charset=utf-8" /><style type="text/css"><!--
#msg dl { border: 1px #006 solid; background: #369; padding:
2020 Jan 07
2
Inline assembly in intel syntax mishandling i constraint
Hi all,
I'm getting rather odd behavior from a call asm inteldialect(). TL;DR is "mov reg, $0" with a "i" constraint on $0 is behaving identical to "mov reg, dword ptr [$0]" and differently from "movl $0, reg" in AT&T syntax.
I'm not sure how to get clang to emit an inteldialect, so for this example, I'm emitting llvm and then modifying
2008 May 11
4
Choosing a Sizer
Following alex advices, i''ve used both "text/textctrl.rb" and
"etc/threaded.rb" to build my first wxApp.
I''ve changed the Sizer type mainly (from "Wx::BoxSizer" to
"Wx::FlexGridSizer").
I didn''t find the way to let @log (Wx::TextCtrl) span 2 columns. At the time
of writing it''s growing only vertically.
And also how to get
2018 Feb 12
0
[inline-asm][asm-goto] Supporting "asm goto" in inline assembly
FYI there is now serious talk of the Linux kernel dropping support for
compilers that *don't* support asm goto.
On Tue, 2017-04-04 at 13:13 -0700, Matthias Braun via llvm-dev wrote:
>
> > On Apr 4, 2017, at 11:44 AM, John McCall via llvm-dev
> > ts.llvm.org> wrote:
> >
> > > On Apr 4, 2017, at 2:12 PM, Matthias Braun <matze at braunis.de>
> >
2020 Jan 08
2
Inline assembly in intel syntax mishandling i constraint
> On Jan 7, 2020, at 18:41, Craig Topper <craig.topper at gmail.com> wrote:
>
> What version of llvm are you using? This looks like it may be fixed on trunk.
After poking at my installation of rust, I'm not entirely sure what version of LLVM it uses. Looking at the GitHub page, it looks like Rust maintains their own copy of llvm and cherry picks commits. The C example was
2023 Jul 22
2
plotly
ChatGPT-4:
------ Query: ----------------------------------
Thank you. The `value` in the code example is 2874. The plot shows a large number at the center and a smaller value computed as a delta relative to the `reference` of 4800. But the large value is given as 2870, and the smaller value is given as -1930 i.e. both values are rounded. Can I control the precision of these two numbers?
2006 Dec 20
0
[ wxruby-Bugs-7386 ] Setting Gauge background/foreground colours in wxruby2-preview
Bugs item #7386, was opened at 2006-12-20 06:13
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=218&aid=7386&group_id=35
Category: Incorrect behavior
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Nobody (None)
Assigned to: Kevin Smith (qualitycode)
Summary: Setting Gauge background/foreground colours in wxruby2-preview
Initial
2010 Sep 20
4
[LLVMdev] Supporting Complex Register Allocation Constraints (PBQP Allocator Status Update)
Hi All,
I've just committed some changes to the PBQP allocator which are designed to
make it easier to implement custom register allocation constraints. This is
a quick summary of those changes, and of the status of the PBQP allocator in
general.
First a quick bit of background:
The PBQP allocator is based on ideas described in [1]. I implemented this
algorithm (with the improved heuristic
2023 Jul 21
1
plotly question
As you apparently haven't received any responses yet, I'll try to
suggest something useful. However, I have absolutely zero experience
with plotly, so this is just from general principles and reading the
plot_ly Help file, which says for the "..." arguments:
"Arguments (i.e., attributes) passed along to the trace type. See
schema() for a list of acceptable attributes for a