public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/37377] [4.4 Regression] Bootstrap failure compiling libgcc
Date: Sat, 11 Apr 2009 19:48:00 -0000	[thread overview]
Message-ID: <20090411194832.26254.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37377-226@http.gcc.gnu.org/bugzilla/>



------- Comment #16 from tkoenig at gcc dot gnu dot org  2009-04-11 19:48 -------
Subject: Bug 37377

Author: tkoenig
Date: Sat Apr 11 19:48:19 2009
New Revision: 145965

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=145965
Log:
2009-04-11  Thomas Koenig  <tkoenig@gcc.gnu.org>

        PR fortran/37377
        * libgfortran.h:  Introduce new macros GFC_DIMENSION_LBOUND,
        GFC_DIMENSION_UBOUND,GFC_DIMENSION_STRIDE, GFC_DIMENSION_EXTENT,
        GFC_DIMENSION_SET, GFC_DESCRIPTOR_LBOUND, GFC_DESCRIPTOR_UBOUND,
        GFC_DESCRIPTOR_EXTENT, GFC_DESCRIPTOR_EXTENT_BYTES,
        GFC_DESCRIPTOR_STRIDE, GFC_DESCRIPTOR_STRIDE_BYTES
        * runtime/in_pack_generic.c (internal_pack):  Use new macros
        for array descriptor access.
        * runtime/in_unpack_generic.c (internal_unpack):  Likewise.
        * intrinsics/dtime.c (dtime_sub):  Likewise.
        * intrinsics/cshift0 (cshift0):  Remove argument size,
        calculate directly from the array descriptor.  Use new macros
        for array descriptor access.
        * cshift0_##N:  Remove shift argument in call to cshift0.
        * cshift0_##N_char:  Mark array_length as unused.  Remove
        array_length in call to cshift0.
        * cshift0_##N_char4:  Likewise.
        * intrisics/etime.c:  Use new macros for array descriptor access.
        * intrinsics/stat.c (stat_i4_sub_0):  Likewise.
        (stat_i8_sub_0):  Likewise.
        (fstat_i4_sub):  Likewise.
        (fstat_i8_sub):  Likewise.
        * intrinsics/date_and_time.c (date_and_time):  Likewise.
        (secnds):  Likewise.
        (itime_i4):  Likewise.
        (itime_i8):  Likewise.
        (idate_i4):  Likewise.
        (idate_i8):  Likewise.
        (gmtime_i4):  Likewise.
        (gmtime_i8):  Likewise.
        (ltime_i4):  Likewise.
        (litme_i8):  Likewise.
        * intrinsics/associated.c (associated):  Likewise.
        * intrinsics/eoshift0.c (eoshift0):  Likewise.
        * intriniscs/size.c (size0):  Likewise.
        * intrinsics/random.c (arandom_r4):  Likewise.
        (arandom_r8):  Likewise.
        (arandom_r10):  Likewise.
        (arandom_r16):  Likewise.
        (random_seed_i4):  Likewise.
        (random_seed_i8):  Likewise.
        * io/list_read.c (nml_parse_qualifier):  Likewise.
        (nml_touch_nodes):  Likewise.
        (nml_read_obj):  Likewise.
        (get_name):  Likewise.
        * io/transfer.c (transfer_array):  Likewise.
        (init_loop_spec):  Likewise.
        (st_set_nml_var_dim):  Likewise.
        * io/write.c (nml_write_obj):  Likewise.
        (obj_loop):  Likewise.


Modified:
    branches/fortran-dev/libgfortran/ChangeLog.dev
    branches/fortran-dev/libgfortran/intrinsics/associated.c
    branches/fortran-dev/libgfortran/intrinsics/cshift0.c
    branches/fortran-dev/libgfortran/intrinsics/date_and_time.c
    branches/fortran-dev/libgfortran/intrinsics/dtime.c
    branches/fortran-dev/libgfortran/intrinsics/eoshift0.c
    branches/fortran-dev/libgfortran/intrinsics/etime.c
    branches/fortran-dev/libgfortran/intrinsics/random.c
    branches/fortran-dev/libgfortran/intrinsics/size.c
    branches/fortran-dev/libgfortran/intrinsics/stat.c
    branches/fortran-dev/libgfortran/io/list_read.c
    branches/fortran-dev/libgfortran/io/transfer.c
    branches/fortran-dev/libgfortran/io/write.c
    branches/fortran-dev/libgfortran/libgfortran.h
    branches/fortran-dev/libgfortran/runtime/in_pack_generic.c
    branches/fortran-dev/libgfortran/runtime/in_unpack_generic.c


-- 


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


      parent reply	other threads:[~2009-04-11 19:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-04 20:23 [Bug rtl-optimization/37377] New: " ebotcazou at gcc dot gnu dot org
2008-09-04 20:31 ` [Bug rtl-optimization/37377] " ebotcazou at gcc dot gnu dot org
2008-09-04 20:33 ` ebotcazou at gcc dot gnu dot org
2008-09-04 20:37 ` ebotcazou at gcc dot gnu dot org
2008-09-04 20:47 ` ebotcazou at gcc dot gnu dot org
2008-09-05  4:48 ` hjl dot tools at gmail dot com
2008-09-05  6:25 ` ebotcazou at gcc dot gnu dot org
2008-09-05 13:48 ` hjl dot tools at gmail dot com
2008-09-07 14:00 ` ebotcazou at gcc dot gnu dot org
2008-09-07 15:47 ` ebotcazou at gcc dot gnu dot org
2008-09-07 16:02 ` ebotcazou at gcc dot gnu dot org
2008-09-08 14:12 ` vmakarov at redhat dot com
2008-09-08 15:27 ` ebotcazou at gcc dot gnu dot org
2008-09-09  0:04 ` hjl at gcc dot gnu dot org
2008-09-12 22:58 ` vmakarov at gcc dot gnu dot org
2008-09-13  8:52 ` ebotcazou at gcc dot gnu dot org
2008-09-18 19:58 ` pinskia at gcc dot gnu dot org
2009-04-11 19:48 ` tkoenig at gcc dot gnu dot org [this message]

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=20090411194832.26254.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: 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).