public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gdr at integrable-solutions dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/18987] [3.3/3.4/4.0 regression] [ia64] Extra '.restore sp' in tail call Date: Sat, 08 Jan 2005 04:47:00 -0000 [thread overview] Message-ID: <20050108044732.24630.qmail@sourceware.org> (raw) In-Reply-To: <20041214154235.18987.schwab@suse.de> ------- Additional Comments From gdr at integrable-solutions dot net 2005-01-08 04:47 ------- Subject: Re: [3.3/3.4/4.0 regression] [ia64] Extra '.restore sp' in tail call "wilson at specifixinc dot com" <gcc-bugzilla@gcc.gnu.org> writes: | > according to http://bugs.debian.org/286840 (if that's the same thing), this is | > broken in gcc-3.3 CVS and gcc-3.4 CVS as well. Latest known working version is | > gcc-3.3.5. | | The patch in question is PR 13158. I added it to mainline, but did not | add it to gcc-3.4 CVS because technically it is not a regression, and | hence the rules do not seem to permit me to add it there without special | permission. For gcc-3.3 CVS, I need the branch maintainer's permission, | and I did not get it, though I did not try very hard, so it isn't on the | gcc-3.3 CVS branch either. Red Hat did add it to gcc-3_4-rhl-branch. I must have missed that patch then. | Someone probably added it to the debian gcc sources as a patch on top of | the FSF tree, so for gcc-3.3 and gcc-3.4 this will have to be fixed on | the debian side by adding the patch in this PR also. then, if it is 3.4.x it should go into 3.3.x too. -- Gaby -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18987
next prev parent reply other threads:[~2005-01-08 4:47 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-12-14 15:42 [Bug target/18987] New: [4.0 " schwab at suse dot de 2004-12-14 15:43 ` [Bug target/18987] " schwab at suse dot de 2004-12-15 21:32 ` steven at gcc dot gnu dot org 2004-12-15 22:04 ` schwab at suse dot de 2004-12-17 13:00 ` pinskia at gcc dot gnu dot org 2004-12-18 13:18 ` steven at gcc dot gnu dot org 2004-12-18 13:30 ` steven at gcc dot gnu dot org 2004-12-20 11:46 ` steven at gcc dot gnu dot org 2004-12-20 20:13 ` davidm at hpl dot hp dot com 2004-12-22 22:47 ` debian-gcc at lists dot debian dot org 2004-12-22 22:50 ` [Bug target/18987] [3.3/3.4/4.0 " pinskia at gcc dot gnu dot org 2004-12-22 23:13 ` debian-gcc at lists dot debian dot org 2005-01-08 3:52 ` wilson at specifixinc dot com 2005-01-08 3:56 ` wilson at gcc dot gnu dot org 2005-01-08 4:47 ` gdr at integrable-solutions dot net [this message] 2005-01-11 3:44 ` cvs-commit at gcc dot gnu dot org 2005-01-11 4:06 ` wilson at specifixinc dot com 2005-01-11 7:07 ` [Bug target/18987] [3.3/3.4 " steven at gcc dot gnu dot org 2005-01-11 19:46 ` gdr at integrable-solutions dot net 2005-01-11 21:05 ` wilson at tuliptree dot org 2005-01-13 5:57 ` cvs-commit at gcc dot gnu dot org 2005-01-14 19:16 ` cvs-commit at gcc dot gnu dot org 2005-01-14 19:45 ` cvs-commit at gcc dot gnu dot org 2005-01-14 19:51 ` wilson at gcc dot gnu dot org 2005-01-14 19:53 ` wilson at gcc dot gnu dot org
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=20050108044732.24630.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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: linkBe 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).