public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/45186] [4.6 Regression] Gfortran 4.5.0 emits wrong linenumbers Date: Sun, 05 Sep 2010 18:10:00 -0000 [thread overview] Message-ID: <20100905181029.14234.qmail@sourceware.org> (raw) In-Reply-To: <bug-45186-15015@http.gcc.gnu.org/bugzilla/> ------- Comment #14 from burnus at gcc dot gnu dot org 2010-09-05 18:10 ------- Subject: Bug 45186 Author: burnus Date: Sun Sep 5 18:10:11 2010 New Revision: 163879 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=163879 Log: 2010-09-05 Tobias Burnus <burnus@net-b.de> PR fortran/45186 * trans-intrinsic.c (gfc_conv_intrinsic_sign, gfc_conv_intrinsic_leadz): Use build_call_expr_loc instead of build_call_expr. * trans-expr.c (gfc_conv_expr_present, gfc_conv_missing_dummy, gfc_conv_string_length, gfc_conv_substring, gfc_conv_component_ref, gfc_conv_unary_op, gfc_conv_powi, gfc_conv_cst_int_power, gfc_conv_string_tmp, gfc_conv_concat_op, gfc_conv_expr_op, gfc_build_compare_string, gfc_set_interface_mapping_bounds, gfc_conv_subref_array_arg, gfc_conv_derived_to_class, conv_isocbinding_procedure, gfc_conv_procedure_call, fill_with_spaces, gfc_trans_string_copy, gfc_trans_alloc_subarray_assign, gfc_trans_structure_assign, gfc_trans_pointer_assignment, gfc_trans_scalar_assign, gfc_trans_zero_assign, gfc_trans_array_copy, gfc_trans_array_constructor_copy): Change fold_build[0-9] to fold_build[0-9]_loc. * trans-io.c (set_parameter_const, set_parameter_value, set_parameter_ref, gfc_convert_array_to_string, set_string, set_internal_unit, io_result, set_error_locus, nml_get_addr_expr, build_dt): Ditto. * trans-openmp.c (gfc_omp_clause_default_ctor, gfc_omp_clause_copy_ctor, gfc_omp_clause_assign_op, gfc_trans_omp_array_reduction, gfc_trans_omp_atomic, gfc_trans_omp_do): Ditto. * trans.c (gfc_add_modify, gfc_build_addr_expr, gfc_build_array_ref, gfc_trans_runtime_error_vararg, gfc_trans_runtime_check, gfc_call_malloc, gfc_allocate_with_status, gfc_allocate_array_with_status, gfc_call_free, gfc_deallocate_with_status, gfc_call_realloc): Ditto. Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/convert.c trunk/gcc/fortran/f95-lang.c trunk/gcc/fortran/trans-intrinsic.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45186
next prev parent reply other threads:[~2010-09-05 18:10 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-08-04 21:02 [Bug fortran/45186] New: " nikolay at totalviewtech dot com 2010-08-04 21:03 ` [Bug fortran/45186] " nikolay at totalviewtech dot com 2010-08-05 11:13 ` [Bug fortran/45186] [4.5/4.6 Regression] " jv244 at cam dot ac dot uk 2010-08-11 0:11 ` pinskia at gcc dot gnu dot org 2010-08-13 9:33 ` mikael at gcc dot gnu dot org 2010-08-13 10:11 ` jv244 at cam dot ac dot uk 2010-08-13 15:11 ` jvdelisle at gcc dot gnu dot org 2010-08-13 17:24 ` jvdelisle at gcc dot gnu dot org 2010-08-13 18:21 ` jv244 at cam dot ac dot uk 2010-08-16 10:16 ` jakub at gcc dot gnu dot org 2010-08-16 10:48 ` jakub at gcc dot gnu dot org 2010-08-17 6:55 ` jakub at gcc dot gnu dot org 2010-08-17 9:26 ` [Bug fortran/45186] [4.6 " jakub at gcc dot gnu dot org 2010-08-17 14:59 ` jv244 at cam dot ac dot uk 2010-09-02 11:15 ` rguenth at gcc dot gnu dot org 2010-09-02 14:04 ` burnus at gcc dot gnu dot org 2010-09-03 19:41 ` burnus at gcc dot gnu dot org 2010-09-05 18:10 ` burnus at gcc dot gnu dot org [this message] 2010-09-07 11:38 ` burnus at gcc dot gnu dot org 2010-09-07 15:32 ` burnus at gcc dot gnu dot org 2010-09-07 19:04 ` burnus at gcc dot gnu dot org 2010-09-09 19:33 ` burnus at gcc dot gnu dot org 2010-09-10 6:02 ` burnus at gcc dot gnu dot org 2010-09-10 6:36 ` jv244 at cam dot ac dot uk 2010-09-10 7:25 ` burnus at gcc dot gnu dot org [not found] <bug-45186-4@http.gcc.gnu.org/bugzilla/> 2010-09-29 10:18 ` burnus at gcc dot gnu.org 2010-10-15 12:43 ` burnus at gcc dot gnu.org 2010-10-15 12:46 ` burnus 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=20100905181029.14234.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).