public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/65548] [5 Regression] gfc_conv_procedure_call Date: Fri, 10 Apr 2015 07:19:00 -0000 [thread overview] Message-ID: <bug-65548-4-qY6AE34ilY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65548-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65548 Jürgen Reuter <juergen.reuter at desy dot de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #9 from Jürgen Reuter <juergen.reuter at desy dot de> --- No, I still get an ICE on a slightly different code, will provide a small example later on, but the code looks like this: allocate (phs%m_in (phs%config%n_in), & source = phs_config%flv(:phs_config%n_in, 1)%get_mass ()) so the problem might be the call to a TBP of a derived type component which is an array, where only some components are taken (?) >From gcc-bugs-return-483238-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Apr 10 07:32:22 2015 Return-Path: <gcc-bugs-return-483238-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 105674 invoked by alias); 10 Apr 2015 07:32:21 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 105390 invoked by uid 48); 10 Apr 2015 07:32:17 -0000 From: "thorduri at secnorth dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/65723] uniform_real_distribution isn't uniform. Date: Fri, 10 Apr 2015 07:32:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: thorduri at secnorth dot net X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: <bug-65723-4-vhj2Ug3Nfr@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-65723-4@http.gcc.gnu.org/bugzilla/> References: <bug-65723-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-04/txt/msg00790.txt.bz2 Content-length: 746 https://gcc.gnu.org/bugzilla/show_bug.cgi?ide723 Thordur Bjornsson <thorduri at secnorth dot net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |thorduri at secnorth dot net --- Comment #3 from Thordur Bjornsson <thorduri at secnorth dot net> --- (In reply to Jonathan Wakely from comment #1) > I think this is WONTFIX. If you use from=0, to=2 then it works fine, so use > those as the distribution parameters and then add 0x1p52 to the result. I don't see how this works fine. Could you perhaps provide an example ? See the following gist: https://gist.github.com/thorduri/5b9cc8743e631638cab4
next prev parent reply other threads:[~2015-04-10 7:19 UTC|newest] Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-25 7:11 [Bug fortran/65548] New: [5.0 " juergen.reuter at desy dot de 2015-03-25 7:15 ` [Bug fortran/65548] " juergen.reuter at desy dot de 2015-03-25 9:03 ` [Bug fortran/65548] [5 " jakub at gcc dot gnu.org 2015-03-25 9:03 ` dominiq at lps dot ens.fr 2015-03-27 13:47 ` dominiq at lps dot ens.fr 2015-04-07 14:11 ` vehre at gcc dot gnu.org 2015-04-09 8:26 ` vehre at gcc dot gnu.org 2015-04-10 7:19 ` juergen.reuter at desy dot de [this message] 2015-04-10 13:48 ` dominiq at lps dot ens.fr 2015-04-10 13:50 ` juergen.reuter at desy dot de 2015-04-10 16:48 ` juergen.reuter at desy dot de 2015-04-15 10:06 ` [Bug fortran/65548] [5/6 " vehre at gcc dot gnu.org 2015-04-15 12:48 ` juergen.reuter at desy dot de 2015-04-15 13:03 ` dominiq at lps dot ens.fr 2015-04-17 16:17 ` juergen.reuter at desy dot de 2015-04-17 16:31 ` dominiq at lps dot ens.fr 2015-04-22 12:02 ` jakub at gcc dot gnu.org 2015-04-23 12:51 ` vehre at gcc dot gnu.org 2015-04-23 12:54 ` juergen.reuter at desy dot de 2015-04-23 13:02 ` juergen.reuter at desy dot de 2015-04-23 13:22 ` dominiq at lps dot ens.fr 2015-04-23 13:52 ` juergen.reuter at desy dot de 2015-04-23 15:06 ` juergen.reuter at desy dot de 2015-04-23 15:11 ` dominiq at lps dot ens.fr 2015-04-28 21:55 ` vehre at gcc dot gnu.org 2015-04-28 22:40 ` juergen.reuter at desy dot de 2015-04-29 8:01 ` vehre at gcc dot gnu.org 2015-04-29 8:06 ` juergen.reuter at desy dot de 2015-04-29 8:33 ` vehre at gcc dot gnu.org 2015-04-29 13:19 ` juergen.reuter at desy dot de 2015-05-05 9:12 ` vehre at gcc dot gnu.org 2015-05-05 9:36 ` juergen.reuter at desy dot de 2015-05-05 10:15 ` vehre at gcc dot gnu.org 2015-05-05 12:43 ` juergen.reuter at desy dot de 2015-05-20 14:57 ` vehre at gcc dot gnu.org 2015-05-29 9:06 ` vehre 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-65548-4-qY6AE34ilY@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: 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).