Eric Pouech [mailto:[EMAIL PROTECTED] wrote:
>>Jonathan Schleifer a écrit :
>> ICC supports gcc inline asm. But it doesn't support defining a symbol
>> twice.
>>
>I'm speaking of the inline keyword (especially about extern inline)
Same issue as at least Visual C 6.0 had for standard C code.
R
Alexandre Julliard <[EMAIL PROTECTED]> wrote:
> What version are you using? According to the man page this is
> supposed to be fixed in icc 9.1.
I'm using ICC 9.1:
asgard:~$ icc --version
icc (ICC) 9.1 20060706
--
Jonathan
Alexandre Julliard a écrit :
But here you really have two non-inline definitions, one in C and one
in assembly. What happens if you remove the C version?
sorry, I redid my week end tests and went too fast
the real "bad" case is:
/* case with 2 C declarations */
extern inline int foo(int a);
Eric Pouech <[EMAIL PROTECTED]> writes:
> it's fixed for C functions, but not when the function is declared in
> assembly
> extern inline int foo(int a);
> extern inline int foo(int a) {return a + 1;}
> int foo(int a) {return a+1;}
> extern inline int ffo(int a);
> extern inline int ffo(int a) {re
Alexandre Julliard a écrit :
Jonathan Schleifer <[EMAIL PROTECTED]> writes:
Eric Pouech <[EMAIL PROTECTED]> wrote:
it seems now the major hurdle is that icc doesn't support
the inline conventions of GCC (and is likely C99 compliant in that
ICC supports gcc inline asm. But it d
Jonathan Schleifer a écrit :
Eric Pouech <[EMAIL PROTECTED]> wrote:
it seems now the major hurdle is that icc doesn't support
the inline conventions of GCC (and is likely C99 compliant in that
ICC supports gcc inline asm. But it doesn't support defining a symbol
twice.
I'm speaki
Jonathan Schleifer <[EMAIL PROTECTED]> writes:
> Eric Pouech <[EMAIL PROTECTED]> wrote:
>
>> it seems now the major hurdle is that icc doesn't support
>> the inline conventions of GCC (and is likely C99 compliant in that
>
> ICC supports gcc inline asm. But it doesn't support defining a symbol
> t
Eric Pouech <[EMAIL PROTECTED]> wrote:
> it seems now the major hurdle is that icc doesn't support
> the inline conventions of GCC (and is likely C99 compliant in that
ICC supports gcc inline asm. But it doesn't support defining a symbol
twice.
--
Jonathan
Jonathan Schleifer a écrit :
"Steven Edwards" <[EMAIL PROTECTED]> wrote:
I had it installed before but its been a while. I never could get
anything other than console apps to work, which I assumed could be do
to a calling convention mismatch like Eric spoke about. I'd be
interested in seeing
"Steven Edwards" <[EMAIL PROTECTED]> wrote:
> I had it installed before but its been a while. I never could get
> anything other than console apps to work, which I assumed could be do
> to a calling convention mismatch like Eric spoke about. I'd be
> interested in seeing bench marks of Wine compil
On 4/21/07, Jonathan Schleifer <[EMAIL PROTECTED]> wrote:
I'm sure someone on the list has icc.
I had it installed before but its been a while. I never could get
anything other than console apps to work, which I assumed could be do
to a calling convention mismatch like Eric spoke about. I'd be
Eric Pouech <[EMAIL PROTECTED]> wrote:
> last time I checked ICC, it didn't support calling conventions
> (cdecl, stdcall...). If we don't have those, it won't be possible to
> support native binaries, and only use ICC for winelib applications
> (even on x86). Unless ICC has these features, it's t
Maarten Lankhorst <[EMAIL PROTECTED]> wrote:
> Wine could build fine without c++, not sure why everything has to
> link against the c++ library as it will probably only be needed in
> winegcc. Also these compiling flags seem kind of agressive.
As I said, just quoted from my .profile, nothing spec
For some strange reason, this mail didn't appear on the list. Therefore
I resent it. (Maybe it's missing because it included an attached GPG
signature?)
Eric Pouech <[EMAIL PROTECTED]> wrote:
> last time I checked ICC, it didn't support calling conventions
> (cdecl, stdcall...). If we don't have
Maarten Lankhorst <[EMAIL PROTECTED]> wrote:
> Ok, Please when responding add wine-devel to CC so others can follow
> discussion.
Forgot that, just hit reply. Did that now.
> It's working well for gcc
Which means nothing since gcc often has a very strange, non-standard
behaviour.
> so I would
For some strange reason, this mail didn't appear on the list. Therefore
I resent it. (Maybe it's missing because it included an attached GPG
signature?)
Maarten Lankhorst <[EMAIL PROTECTED]> wrote:
> Ok, Please when responding add wine-devel to CC so others can follow
> discussion.
Forgot that,
For some strange reason, this mail didn't appear on the list. Therefore
I resent it. (Maybe it's missing because it included an attached GPG
signature?)
Maarten Lankhorst <[EMAIL PROTECTED]> wrote:
> Wine could build fine without c++, not sure why everything has to
> link against the c++ library
It seems my replies never got through because I wasn't subscribed to the
list, but instead using gmane. I subscribed now and resent all my
replies.
Maarten Lankhorst <[EMAIL PROTECTED]> wrote:
> Ok, Please when responding add wine-devel to CC so others can follow
> discussion.
Forgot that, jus
It seems my replies never got though because I wasn't subscribed to the
list, but instead using gmane. I subscribed now and resent all my
replies.
Maarten Lankhorst <[EMAIL PROTECTED]> wrote:
> Wine could build fine without c++, not sure why everything has to
> link against the c++ library as it
It seems my replies never got through because I wasn't subscribed to the
list, but instead using gmane. I subscribed now and resent all my
replies.
Eric Pouech <[EMAIL PROTECTED]> wrote:
> last time I checked ICC, it didn't support calling conventions
> (cdecl, stdcall...). If we don't have thos
Maarten Lankhorst a écrit :
Jonathan Schleifer schreef:
Maarten Lankhorst <[EMAIL PROTECTED]> wrote:
Wine could build fine without c++, not sure why everything has to
link against the c++ library as it will probably only be needed in
winegcc. Also these compiling flags seem kind of a
Jonathan Schleifer schreef:
> Maarten Lankhorst <[EMAIL PROTECTED]> wrote:
>
>> Wine could build fine without c++, not sure why everything has to
>> link against the c++ library as it will probably only be needed in
>> winegcc. Also these compiling flags seem kind of agressive.
>>
>
> As I
Jonathan Schleifer schreef:
> Hi!
>
> This patch makes it possible to build an run wine with the Intel
> compiler.
>
> Here are the environment variables I used to build:
>
> export CFLAGS="-O3 -xP -msse3 -parallel"
> export CXX="icc"
> export CXXFLAGS="-O3 -xP -msse3 -parallel"
> export LDFLAGS="-
Hi!
This patch makes it possible to build an run wine with the Intel
compiler.
Here are the environment variables I used to build:
export CC="icc"
export CFLAGS="-O3 -xP -msse3 -parallel"
export CXX="icc"
export CXXFLAGS="-O3 -xP -msse3 -parallel"
export LDFLAGS="-lguide -lsvml -lstdc++ -paralle
24 matches
Mail list logo
