On Mon, Feb 23, 2009 at 7:48 PM, H.J. Lu wrote:
> On Mon, Feb 23, 2009 at 10:39 AM, Jiri Olsa wrote:
>> On Mon, Feb 23, 2009 at 7:35 PM, H.J. Lu wrote:
>>> On Mon, Feb 23, 2009 at 10:05 AM, Jiri Olsa wrote:
Hi,
my shared library crashes with movaps instruction using not aligned m
Hello,
Can someone *please* ban this nutcase from the wiki?
There is almost weekly spam added to the wiki from this account.
Thanks,
Gr.
Steven
On Mon, Feb 23, 2009 at 07:30:24PM -0800, S. Beck wrote:
> (Pleas read twice before you start to answer !)
The gcc list is for the development of GCC itself, not development with
GCC, not discussion of misfeatures in a particular programming language.
Hello together.
(Pleas read twice before you start to answer !)
There are now 3 projects I know using NASM for there backend tasks and link it
together with the front end c++ code.
I think I do the same, until c++ has a pointer object (reserved word, type
like object_ptr myallover_ptr) that can
Joern Rennecke writes:
>> By the way: Are there better places to ask such questions like in gcc-help?
>
> If you actually need a new gcc backend and want it to be done well. you
> should instruct an experienced contractor to do it for you, or hire an
> in-house expert.
>
> Your question reveals t
On Mon, Feb 23, 2009 at 10:39 AM, Jiri Olsa wrote:
> On Mon, Feb 23, 2009 at 7:35 PM, H.J. Lu wrote:
>> On Mon, Feb 23, 2009 at 10:05 AM, Jiri Olsa wrote:
>>> Hi,
>>>
>>> my shared library crashes with movaps instruction using not aligned memory.
>>>
>>> Since the shared library function is bein
On Mon, Feb 23, 2009 at 7:35 PM, H.J. Lu wrote:
> On Mon, Feb 23, 2009 at 10:05 AM, Jiri Olsa wrote:
>> Hi,
>>
>> my shared library crashes with movaps instruction using not aligned memory.
>>
>> Since the shared library function is being called from dynamic linker, which
>> basically prepares th
On Mon, Feb 23, 2009 at 10:05 AM, Jiri Olsa wrote:
> Hi,
>
> my shared library crashes with movaps instruction using not aligned memory.
>
> Since the shared library function is being called from dynamic linker, which
> basically prepares the memory location, I'm not sure whoose side issues this
Hi,
my shared library crashes with movaps instruction using not aligned memory.
Since the shared library function is being called from dynamic linker, which
basically prepares the memory location, I'm not sure whoose side issues this is.
I have following function in C:
typedef float La_x86_64_x
Jack Howarth wrote:
> The same issue in the libiberty testsuite run can be seen with
> the Apple regress server log at
> http://gcc.gnu.org/regtest/HEAD/native-lastbuild.txt.gzip.
> If you search for test-demangle, you will find...
I'm sure there is a bugzilla entry for that.
Paolo
10 matches
Mail list logo