public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/59436] [4.9 Regression] FAIL: 17_intro/headers/c++200x/stdc++.cc (test for excess errors)
Date: Thu, 19 Dec 2013 21:54:00 -0000	[thread overview]
Message-ID: <bug-59436-4-hLynL44H2W@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59436-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59436

H.J. Lu <hjl.tools at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hjl.tools at gmail dot com

--- Comment #16 from H.J. Lu <hjl.tools at gmail dot com> ---
The bad run has

open("x86_64-unknown-linux-gnu/bits/stdc++.h.gch/O2ggnu++0x.gch",
O_RDONLY|O_NOCTTY) = 5
fstat(5, {st_mode=S_IFREG|0644, st_size=78195440, ...}) = 0
read(5, "gpch+014l\272\361U\305\242H\350\25\237\343\320\316\t\376\323", 24) =
24
read(5, "\3\1\0\0\0\0\0\0\200\367x\0\0\0\0\0\340\0\0\0\0\0\0\0", 24) = 24
...
read(5,
"r\5\0\20\0\0\0\340r\5\0\20\0\0\0\340r\5\0\20\0\0\0\340r\5\0\20\0\0\0\340"...,
4096) = 4096
read(5, "v\5\0\20\0\0\0p\236L\2\20\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
4096) = 4096
read(5, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
4096) = 4096
read(5, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
4096) = 4096
read(5, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
4096) = 4096
read(5, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
4096) = 4096
mmap(0x1000000000, 77393920, PROT_READ|PROT_WRITE, MAP_PRIVATE, 5, 0xc1000) =
0x1000000000
...

The good runs don't do mmap on PCH file.


  parent reply	other threads:[~2013-12-19 21:54 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-09 18:00 [Bug libstdc++/59436] New: " ubizjak at gmail dot com
2013-12-09 18:02 ` [Bug libstdc++/59436] " ubizjak at gmail dot com
2013-12-09 18:14 ` ubizjak at gmail dot com
2013-12-09 18:50 ` ubizjak at gmail dot com
2013-12-12 13:36 ` jakub at gcc dot gnu.org
2013-12-13  9:53 ` ubizjak at gmail dot com
2013-12-16 16:07 ` hjl.tools at gmail dot com
2013-12-16 17:42 ` jakub at gcc dot gnu.org
2013-12-16 17:44 ` [Bug libstdc++/59436] [4.9 Regression] " jakub at gcc dot gnu.org
2013-12-16 17:57 ` hjl.tools at gmail dot com
2013-12-16 18:12 ` hjl.tools at gmail dot com
2013-12-18 12:56 ` dominiq at lps dot ens.fr
2013-12-18 14:58 ` jakub at gcc dot gnu.org
2013-12-19 10:06 ` jakub at gcc dot gnu.org
2013-12-19 21:54 ` hjl.tools at gmail dot com [this message]
2013-12-19 22:01 ` hjl.tools at gmail dot com
2013-12-19 22:12 ` hjl.tools at gmail dot com
2013-12-29  9:29 ` trippels at gcc dot gnu.org
2013-12-29  9:31 ` trippels at gcc dot gnu.org
2014-01-02 11:47 ` [Bug pch/59436] " trippels at gcc dot gnu.org
2014-01-07  7:48 ` jakub at gcc dot gnu.org
2014-01-07 16:50 ` jakub at gcc dot gnu.org
2014-01-07 16:52 ` jakub at gcc dot gnu.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=bug-59436-4-hLynL44H2W@http.gcc.gnu.org/bugzilla/ \
    --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: 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).