Displaying 20 results from an estimated 1000 matches similar to: "Suffix or Operands invalid during AMD64 compile"
2009 Jul 14
4
error on solaris please help interlocked*functions
i install the wine 1.1.25 but after awhile installation stops
and heres some detail in terminal
> configure: libcapi20 development files not found, ISDN won't be supported.
> configure: libldap (OpenLDAP) development files not found, LDAP won't be supported.
>
> configure: Finished. Do 'make depend && make' to compile Wine.
>
> cc -c -I. -I.
2008 Oct 18
1
end of line not at end of line (Compile error) (V1.0.1&1.0.6
http://www.linuxquestions.org/questions/fedora-35/fedora-core-9-compile-error-wine1.0.1-and-1.0.6-677151/
ct-aliasing -Wdeclaration-after-statement -Wwrite-strings -Wtype-limits -Wpointer-arith -g -O2 -o menu.o menu.c
{standard input}: Assembler messages:
{standard input}:7413: Warning: end of file not at end of a line; newline inserted
gcc: Internal error: Segmentatiefout (program cc1)
Please
2009 Jan 15
3
Assembler errors in interlocked.c 0.9.61/1.1.12
Hi. I've decided to do a regression test in order to find out what's wrong with Dreamfall (see AppDB), and that involves comparing releases 0.9.61 and 1.1.12 (reports have been "garbage" ever since 1.0.0, but with errors different from mine). However, when building for the first time, this error occurs:
Code:
ccache gcc -c -I. -I. -I../../include -I../../include -D__WINESRC__
2009 Sep 11
2
WINE with 64-bit Support Build on Snow Leopard
Hello WINE Users:
I am trying to build WINE on Snow Leopard with 64-bit support enabled (actually for my particular purpose I need to build a version of WINE with both 32-bit and 64-bit libraries supported). I am using the 1.1.29 source version..
I have been following the guide for building on Mac and 64-bit WINE at:
http://wiki.winehq.org/MacOSX/Building
http://wiki.winehq.org/Wine64
I get
2012 Aug 13
1
[LLVMdev] [RFC] Bundling support in the PostRA Scheduler
Hi all,
Thanks for your feed-backs :-)
@Andrew: In fact, I've reused most of the postRA list scheduler code and
the resource priority queue. Every time it needs to move forward, either
because of a res hazard (HazardRec) or an invalid combination of
instructions in the current packet (DFA), it closes the current bundle
and advances to the next cycle. The non-interlocked nature of our
2012 Aug 06
0
[LLVMdev] [RFC] Bundling support in the PostRA Scheduler
On Jul 31, 2012, at 8:37 AM, Ivan Llopard <ivanllopard at gmail.com> wrote:
> Hi,
>
> I'm working on a custom top-down post RA scheduler which builds bundles
> at the same time for our VLIW processor. I've borrowed most of the
> implementation from the resource priority queue implemented for the
> existent VLIW scheduler but applied to the context of MI
2012 Jul 31
6
[LLVMdev] [RFC] Bundling support in the PostRA Scheduler
Hi,
I'm working on a custom top-down post RA scheduler which builds bundles
at the same time for our VLIW processor. I've borrowed most of the
implementation from the resource priority queue implemented for the
existent VLIW scheduler but applied to the context of MI scheduling.
Basically, instructions that are likely to be bundled must be scheduled
first (i.e. get higher priority).
2012 Apr 23
0
[LLVMdev] [RFC] Scheduler Rework
On Apr 20, 2012, at 10:31 AM, dag at cray.com wrote:
> I'd like to begin a project to rework the scheduler to address some
> problems we've discovered on this end. The goal is to get a more
> configurable/flexible scheduler while simplifying maintenance by
> separating policy from implementation to get independent and
> interchangeable parts.
>
> This is going to be
2012 May 11
0
[LLVMdev] Scheduler Roadmap
On May 10, 2012, at 9:06 PM, Hal Finkel <hfinkel at anl.gov> wrote:
>> - Target pass configuration: DONE
>> - MachineScheduler pass framework: DONE
>> - MI Scheduling DAG: DONE
>> - AliasAnalysis aware DAG option: In review (Sergei)
>> - Bidirectional list scheduling: DONE
>> - LiveInterval Update: WIP (simple instruction reordering is
>> supported)
2011 Jun 01
5
Status of Wine64 on OSX?
Hi,
I know Wine64 is still experimental, and I've read threads from last Summer stating that Wine64 won't build nor run on OSX at this time.
However, Wine64 would be really useful for me on OSX, because I build small simple apps for both win32 and win64 mode, and being able to crosscompile and run them from OSX would be a great time saver for me.
So, what's the status of Wine64 on
2011 Aug 23
2
Can't install program with today's git in 64-bit
<head><style>body{font-family: Geneva,Arial,Helvetica,sans-serif;font-size:9pt;background-color: #ffffff;color: black;}</style></head><body id="compText">>I downloaded today''s git, compiled --enable-win64, and installed. <br>>The command "wine64 notepad" produces notepad, and everything seems fine. <br>>But then I
2012 Mar 10
12
Compiling & running 1.4 on 64bit
I need someone's expertise.
I have compiled wine 1.4-1 in a Xubuntu 12.04 beta, running on virtual machine (obviously a 32bit system, since it's VM).
Steps i took:
Code:
1. installed development packages by running http://winezeug.googlecode.com/svn/trunk/install-wine-deps.sh (as instructed on http://wiki.winehq.org/Wine64)
2. apt-get build-dep wine
3. apt-get install patch libpulse-dev
2011 Mar 19
5
64-bit installation instructions
<head><style>body{font-size:10pt;font-family:arial,sans-serif;background-color:#ffffff;color:black;}p{margin:0px;}</style></head><body>>Have you also compiled 32 bit Wine? My impression is that you need both to have a functioning system. http://wiki.winehq.org/Wine64<br><br>Thanks. I followed instructions. It seems to be OK to use two git repositories
2011 Feb 15
11
Is Wine64 usable yet?
Hi,
I am trying to get a general feel of how usable Wine64 is.
I just built 1.3.13.
To see how well it works, I ran 64-bit Putty. It works flawlessly.
Now, I am trying to play around with different little programs. I took
"notepad.exe" from a Windows 7 install (hoping it would be a reasonably
simple program for a start). It crashed with:
fixme:heap:HeapSetInformation (nil) 1 (nil)
2012 Apr 24
2
[LLVMdev] [RFC] Scheduler Rework
Andrew Trick <atrick at apple.com> writes:
> We plan to move to the MachineScheduler by 3.2. The structure is:
How hard will this be to backport to 3.1? Has woprk on this started
yet?
> ScheduleDAG: Abstract DAG of SUnits and SDeps
> |
> v
> ScheduleDAGInstrs: Build the DAG from MachineInstrs, each SUnit tied to an MI
> Delimit the current
2008 Apr 18
2
[LLVMdev] Function materializing in Java
Hi everyone,
I would like to apply the following patch (java-materialize.patch) in
order to materialize Java functions in vmkit. The current implementation
is not satisfactory because the materializeFunction of a module provider
is not supposed to do anything but read the bitcode, which is not the
case in Java. In Java, materializing a function Foo can possibly trigger
class loading (hence
2009 Jan 26
4
Error while building wine 1.1.13 on Mac Os X
As in subject, when I try building wine 1.1.13 using Mac OS X 10.5.6 using both the latest developer tools and fink packages (for libjpeg, libpng, libxml2, etc) it gives an error on "make && make depend" with the following message:
--
rm -f libwine_port.a
ar rc libwine_port.a ffs.o fstatvfs.o futimes.o getopt.o getopt1.o getpagesize.o gettid.o interlocked.o isinf.o isnan.o
2011 Apr 12
2
Re: Is Wine64 usable yet?
Hmm.. is this "update.exe" problem same which is happening with ie7 in32-bit (needs some cat file copied somewhere to run)?
With wow64 build I have been testing to install SolidWorks 2009-2011 x64 and most of the times installer tries by default install the app to "Program Files (x86)"-folder, sometimes it gets correct program files folder, usually not. Installer fails on
2008 Dec 24
5
Yesterday's Git updates break compilation for anyone else?
Updated git last night (been compiling fine for years), and now get:
../../tools/widl/widl -I. -I. -I../../include -I../../include -D__WINESRC__ -h -H ../../include/wtypes.h ../../include/wtypes.idl
make[2]: ../../tools/widl/widl: Command not found
make[2]: *** [../../include/wtypes.h] Error 127
Made
2017 Dec 01
2
Schedules, latency and register liveness for complex instructions
Hi Martin,
> The CPU that I am targeting is VLIW with no hardware interlocking
(the next instruction does not wait for the previous to complete). This
leads to fairly complex scheduling, but can be generally accommodated
well in LLVM.
Thanks for sharing your usecase about instruction scheduling, I am
learning Instruction Selector by reading ARM and AMDGPU target's source
code, then