public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/30672]  New: Internal compiler error: segment violation
@ 2007-02-01 20:46 lgcota at gmail dot com
  2007-02-01 20:49 ` [Bug fortran/30672] " pinskia at gcc dot gnu dot org
                   ` (6 more replies)
  0 siblings, 7 replies; 8+ messages in thread
From: lgcota at gmail dot com @ 2007-02-01 20:46 UTC (permalink / raw)
  To: gcc-bugs

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1342 bytes --]

error interno del compilador: Violación de segmento

/home/lgc/irun/bin/../libexec/gcc/i386-pc-linux-gnu/4.3.0/f951 ../dynamic.f
-ffixed-form -quiet -dumpbase dynamic.f -mtune=i386 -auxbase dynamic -O2
-version -ffixed-line-length-132 -I.. -fintrinsic-modules-path
/home/lgc/irun/bin/../lib/gcc/i386-pc-linux-gnu/4.3.0/finclude -o dynamic.s
GNU F95 version 4.3.0 20070131 (experimental) (i386-pc-linux-gnu)
        compiled by GNU C version 4.3.0 20070131 (experimental).
GGC heurísticas: --param ggc-min-expand=100 --param ggc-min-heapsize=131072

------- code segment below -------

 else
        kvf(1:3,1:3) = kv(1:3,1:3)
      endif

----------------------------------

Please I don't want to annoy you but the instructions to file a bug are really
hard to follow and lengthy. I haven't been able to produce the "*.i* file, but
just the ".s" one. Please mail me if you want me to send you the whole package
or else give me other instructions.

Thank you.


-- 
           Summary: Internal compiler error: segment violation
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: lgcota at gmail dot com


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


^ permalink raw reply	[flat|nested] 8+ messages in thread

* [Bug fortran/30672] Internal compiler error: segment violation
  2007-02-01 20:46 [Bug fortran/30672] New: Internal compiler error: segment violation lgcota at gmail dot com
@ 2007-02-01 20:49 ` pinskia at gcc dot gnu dot org
  2007-02-01 20:54 ` lgcota at gmail dot com
                   ` (5 subsequent siblings)
  6 siblings, 0 replies; 8+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2007-02-01 20:49 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #1 from pinskia at gcc dot gnu dot org  2007-02-01 20:49 -------
(In reply to comment #0)
> Please I don't want to annoy you but the instructions to file a bug are really
> hard to follow and lengthy. I haven't been able to produce the "*.i* file, but
> just the ".s" one. Please mail me if you want me to send you the whole package
> or else give me other instructions.

Those instrunctions are more for C/C++ bug filing.
Does the code use modules?
If not can you just attach dynamic.f if it is open source?


-- 


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


^ permalink raw reply	[flat|nested] 8+ messages in thread

* [Bug fortran/30672] Internal compiler error: segment violation
  2007-02-01 20:46 [Bug fortran/30672] New: Internal compiler error: segment violation lgcota at gmail dot com
  2007-02-01 20:49 ` [Bug fortran/30672] " pinskia at gcc dot gnu dot org
@ 2007-02-01 20:54 ` lgcota at gmail dot com
  2007-02-01 21:44 ` kargl at gcc dot gnu dot org
                   ` (4 subsequent siblings)
  6 siblings, 0 replies; 8+ messages in thread
From: lgcota at gmail dot com @ 2007-02-01 20:54 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #2 from lgcota at gmail dot com  2007-02-01 20:54 -------
I could attach the 'dynamic.f' file if you tell me how (or is it just to
cut-and-paste it?). The file is NOT open source but is free for academic use.
It DOES use modules.


-- 

lgcota at gmail dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |lgcota at gmail dot com


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


^ permalink raw reply	[flat|nested] 8+ messages in thread

* [Bug fortran/30672] Internal compiler error: segment violation
  2007-02-01 20:46 [Bug fortran/30672] New: Internal compiler error: segment violation lgcota at gmail dot com
  2007-02-01 20:49 ` [Bug fortran/30672] " pinskia at gcc dot gnu dot org
  2007-02-01 20:54 ` lgcota at gmail dot com
@ 2007-02-01 21:44 ` kargl at gcc dot gnu dot org
  2007-02-01 23:36 ` kargl at gcc dot gnu dot org
                   ` (3 subsequent siblings)
  6 siblings, 0 replies; 8+ messages in thread
From: kargl at gcc dot gnu dot org @ 2007-02-01 21:44 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #3 from kargl at gcc dot gnu dot org  2007-02-01 21:44 -------
Luis,

You can email me the file at sgk@troutmask.apl.washington.edu.
I'll extract a testcase if the failure occurs on my systems.


-- 

kargl at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kargl at gcc dot gnu dot org


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


^ permalink raw reply	[flat|nested] 8+ messages in thread

* [Bug fortran/30672] Internal compiler error: segment violation
  2007-02-01 20:46 [Bug fortran/30672] New: Internal compiler error: segment violation lgcota at gmail dot com
                   ` (2 preceding siblings ...)
  2007-02-01 21:44 ` kargl at gcc dot gnu dot org
@ 2007-02-01 23:36 ` kargl at gcc dot gnu dot org
  2007-02-02  0:08 ` kargl at gcc dot gnu dot org
                   ` (2 subsequent siblings)
  6 siblings, 0 replies; 8+ messages in thread
From: kargl at gcc dot gnu dot org @ 2007-02-01 23:36 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #4 from kargl at gcc dot gnu dot org  2007-02-01 23:36 -------
Just a quick note.  dynamic.f will compile without optimization.
I can reproduce the problem.  Now to reduce it to something managable.


-- 


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


^ permalink raw reply	[flat|nested] 8+ messages in thread

* [Bug fortran/30672] Internal compiler error: segment violation
  2007-02-01 20:46 [Bug fortran/30672] New: Internal compiler error: segment violation lgcota at gmail dot com
                   ` (3 preceding siblings ...)
  2007-02-01 23:36 ` kargl at gcc dot gnu dot org
@ 2007-02-02  0:08 ` kargl at gcc dot gnu dot org
  2007-02-02  0:12 ` kargl at gcc dot gnu dot org
  2007-02-02  0:28 ` pinskia at gcc dot gnu dot org
  6 siblings, 0 replies; 8+ messages in thread
From: kargl at gcc dot gnu dot org @ 2007-02-02  0:08 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #5 from kargl at gcc dot gnu dot org  2007-02-02 00:08 -------
Reduced testcase


module current
   integer, save :: ndim
   real, save :: kv(3,3)
end module current

subroutine dynamic

   use current

   implicit none

   real :: kvf(3,3)

   if (ndim .eq. 3) then
      call kvector3Df(kvf)
   else
      kvf(1:3,1:3) = kv(1:3,1:3)
   end if

end subroutine dynamic



troutmask:sgk[372] gfc4x -c -O zxc.f90
zxc.f90: In function 'dynamic':
zxc.f90:17: internal compiler error: in operand_equal_p, at fold-const.c:2557
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.


-- 


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


^ permalink raw reply	[flat|nested] 8+ messages in thread

* [Bug fortran/30672] Internal compiler error: segment violation
  2007-02-01 20:46 [Bug fortran/30672] New: Internal compiler error: segment violation lgcota at gmail dot com
                   ` (4 preceding siblings ...)
  2007-02-02  0:08 ` kargl at gcc dot gnu dot org
@ 2007-02-02  0:12 ` kargl at gcc dot gnu dot org
  2007-02-02  0:28 ` pinskia at gcc dot gnu dot org
  6 siblings, 0 replies; 8+ messages in thread
From: kargl at gcc dot gnu dot org @ 2007-02-02  0:12 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #6 from kargl at gcc dot gnu dot org  2007-02-02 00:12 -------
Further reduction is possible.

subroutine dynamic(ndim, kv)
   implicit none
   integer :: ndim
   real :: kvf(3,3), kv(3,3)
   if (ndim .eq. 3) then
      call kvector3Df(kvf)
   else
      kvf(1:3,1:3) = kv(1:3,1:3)
   end if
end subroutine dynamic


-- 


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


^ permalink raw reply	[flat|nested] 8+ messages in thread

* [Bug fortran/30672] Internal compiler error: segment violation
  2007-02-01 20:46 [Bug fortran/30672] New: Internal compiler error: segment violation lgcota at gmail dot com
                   ` (5 preceding siblings ...)
  2007-02-02  0:12 ` kargl at gcc dot gnu dot org
@ 2007-02-02  0:28 ` pinskia at gcc dot gnu dot org
  6 siblings, 0 replies; 8+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2007-02-02  0:28 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #7 from pinskia at gcc dot gnu dot org  2007-02-02 00:28 -------


*** This bug has been marked as a duplicate of 30391 ***


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |DUPLICATE


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


^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2007-02-02  0:28 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-02-01 20:46 [Bug fortran/30672] New: Internal compiler error: segment violation lgcota at gmail dot com
2007-02-01 20:49 ` [Bug fortran/30672] " pinskia at gcc dot gnu dot org
2007-02-01 20:54 ` lgcota at gmail dot com
2007-02-01 21:44 ` kargl at gcc dot gnu dot org
2007-02-01 23:36 ` kargl at gcc dot gnu dot org
2007-02-02  0:08 ` kargl at gcc dot gnu dot org
2007-02-02  0:12 ` kargl at gcc dot gnu dot org
2007-02-02  0:28 ` pinskia at gcc dot gnu dot org

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).