From: Bruce Korb <bkorb@gnu.org>
To: David Miller <davem@davemloft.net>
Cc: gcc@gcc.gnu.org
Subject: Re: fixincl 'make check' regressions...
Date: Tue, 16 Mar 2010 14:50:00 -0000 [thread overview]
Message-ID: <668c430c1003160707x4bb675e2x591d0097f28ed35a@mail.gmail.com> (raw)
In-Reply-To: <20100315.230051.179351226.davem@davemloft.net>
The intent was to clear up some stuff in the README.
When I noticed that I had affected other files, I had tried to put
everything back. Obviously a glitch. I'll fix it when I get home
tonight.
On Mon, Mar 15, 2010 at 11:00 PM, David Miller <davem@davemloft.net> wrote:
>
> Ever since your changes installed on March 12th, I've been getting
> fixincludes testsuite failures of the form below.
>
> I also notice that none of these changes added ChangeLog entries, and
> furthermore the SVN commit messages were extremely terse so it was
> hard to diagnose the intent or reasoning behind your changes.
>
> iso/math_c99.h /home/davem/src/GIT/GCC/gcc/fixincludes/tests/base/iso/math_c99.h differ: char 1366, line 52
> *** iso/math_c99.h Mon Mar 15 22:55:36 2010
> --- /home/davem/src/GIT/GCC/gcc/fixincludes/tests/base/iso/math_c99.h Thu Jan 21 04:06:11 2010
> ***************
> *** 49,55 ****
> ? __builtin_signbitf(x) \
> : sizeof(x) == sizeof(long double) \
> ? __builtin_signbitl(x) \
> ! : __builtin_signbit(x));
> #endif /* SOLARIS_MATH_8_CHECK */
>
>
> --- 49,55 ----
> ? __builtin_signbitf(x) \
> : sizeof(x) == sizeof(long double) \
> ? __builtin_signbitl(x) \
> ! : __builtin_signbit(x))
> #endif /* SOLARIS_MATH_8_CHECK */
>
>
>
> There were fixinclude test FAILURES
>
next prev parent reply other threads:[~2010-03-16 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 6:48 David Miller
2010-03-16 14:50 ` Bruce Korb [this message]
2010-03-19 11:55 ` David Miller
2010-03-19 16:02 ` Bruce Korb
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=668c430c1003160707x4bb675e2x591d0097f28ed35a@mail.gmail.com \
--to=bkorb@gnu.org \
--cc=davem@davemloft.net \
--cc=gcc@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).