public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: <gcc-patches@gcc.gnu.org>, Paolo Bonzini <bonzini@gnu.org>,
	       Mike Stump <mikestump@comcast.net>,
	DJ Delorie <dj@delorie.com>,
	       Nathanael Nerode <neroden@gcc.gnu.org>,
	       Alexandre Oliva <aoliva@redhat.com>,
	       Gerald Pfeifer <gerald@pfeifer.com>
Subject: Re: [build, driver] RFC: Support compressed debug sections
Date: Tue, 03 Jun 2014 10:40:00 -0000	[thread overview]
Message-ID: <ydd1tv68eei.fsf@lokon.CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <yddr43fabf4.fsf@lokon.CeBiTec.Uni-Bielefeld.DE> (Rainer Orth's	message of "Tue, 27 May 2014 10:11:27 +0200")

Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> writes:

> "Joseph S. Myers" <joseph@codesourcery.com> writes:
[...]
>> Thanks for the explanation.  The driver changes are OK.
>
> Thanks.  I still need approval for the doc and build parts, as well as
> the Darwin and DJGPP changes.  For the latter two, I've included the
> patch in a x86_64-apple-darwin11.4.2 build, verifying that -gz is
> rejected as expected (no idea if the are any working gas and gold ports
> that would support the option).  For DJGPP, I've tried a
> i386-pc-solaris2.11 x i586-pc-msdosdjgpp cross.  While the specs
> additions look correct, trying to compile even the most trivial program
> SEGVs:
[...]

It's been another week, and I still need approval for the build, doc,
and Darwin changes:

	https://gcc.gnu.org/ml/gcc-patches/2014-05/msg01860.html

Thanks.
        Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University

  parent reply	other threads:[~2014-06-03 10:40 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-11 12:36 Rainer Orth
2013-04-11 12:36 ` Andi Kleen
2013-04-11 12:54   ` Rainer Orth
2013-04-26 22:43 ` Joseph S. Myers
2013-04-30 15:06   ` Rainer Orth
2013-05-03 20:01     ` Joseph S. Myers
2013-05-04 21:20       ` Rainer Orth
2013-05-05 14:15         ` Joseph S. Myers
2013-05-15 15:38           ` Rainer Orth
2014-05-22 11:45           ` Rainer Orth
2014-05-22 15:49             ` Joseph S. Myers
2014-05-22 16:19               ` Rainer Orth
2014-05-22 16:33                 ` Joseph S. Myers
2014-05-27  8:11                   ` Rainer Orth
2014-05-27 17:06                     ` DJ Delorie
2014-06-03 10:40                     ` Rainer Orth [this message]
2014-06-03 16:20                       ` Mike Stump
2014-06-04  8:54                         ` Rainer Orth
2014-06-04 11:08                           ` Mike Stump
2014-06-04 18:09                           ` Eric Christopher
2014-06-26 13:32                             ` Rainer Orth
2014-06-27 16:33                               ` Eric Christopher
2014-06-03 23:47                       ` Gerald Pfeifer
2014-06-26 13:16                         ` Rainer Orth
2014-06-27 13:01                           ` Paolo Bonzini

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=ydd1tv68eei.fsf@lokon.CeBiTec.Uni-Bielefeld.DE \
    --to=ro@cebitec.uni-bielefeld.de \
    --cc=aoliva@redhat.com \
    --cc=bonzini@gnu.org \
    --cc=dj@delorie.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --cc=joseph@codesourcery.com \
    --cc=mikestump@comcast.net \
    --cc=neroden@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: 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).