public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Matthias Drochner <M.Drochner@fz-juelich.de>
To: Vivek Raheja <vivek@cadence.com>
Cc: pinskia@gcc.gnu.org, gcc-bugs@gcc.gnu.org, vivek@janoon.cadence.com
Subject: Re: Regarding : gcc emitting "movaps" to unaligned memory
Date: Mon, 07 Jun 2004 14:58:00 -0000	[thread overview]
Message-ID: <200406071356.PAA0000044042@zel459.zel.kfa-juelich.de> (raw)
In-Reply-To: Your message of "Tue, 01 Jun 2004 15:58:11 +0530." <200406011028.i51ASBr11744@janoon.cadence.com>


vivek@cadence.com said:
>  While porting my 64bit application on opteron amd64,
>  I am facing issues in "printf/vprintf/ vsprintf calls". 

Yep - this looks a lot the problem I had.
In my case (NetBSD) the culprit was the OS code which
sets up the stacks during thread creation and signal
handler invocation -- it got it wrong. (One has to think
twice if the user code is jumped to through a fake function
call return...)

> We are using libc-2.3.2.so

Sorry, I don't follow glibc development. Are there threads
involved or other userland scheduling things as setcontext()?

(Btw, there are still alignment issues in gcc-3.4 which show up
with Ada. Was reported by John R. Shannon in the gcc mailing
list.)

best regards
Matthias



      reply	other threads:[~2004-06-07 14:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-01 10:28 Vivek Raheja
2004-06-07 14:58 ` Matthias Drochner [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200406071356.PAA0000044042@zel459.zel.kfa-juelich.de \
    --to=m.drochner@fz-juelich.de \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=pinskia@gcc.gnu.org \
    --cc=vivek@cadence.com \
    --cc=vivek@janoon.cadence.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).