[Bug other/44116] 64bit inodes for source code causes Value too large for defined data type (XFS,inode64)

[gcc at breakpoint dot cc]

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



Sebastian Andrzej Siewior gcc at breakpoint dot cc changed:



   What|Removed |Added



 CC||gcc at breakpoint dot cc,

   ||iant at google dot com



--- Comment #5 from Sebastian Andrzej Siewior gcc at breakpoint dot cc 
2013-02-07 21:17:46 UTC ---

I run into this myself today with an older compiler. This has been fixed in svn

commit 166230. The fix is part of gcc-4.6.0+ and it does not look like it has

been backported.

It can be closed now :)

[Bug other/44116] 64bit inodes for source code causes Value too large for defined data type (XFS,inode64)

[pinskia at gcc dot gnu.org]

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



Andrew Pinski pinskia at gcc dot gnu.org changed:



   What|Removed |Added



 Status|UNCONFIRMED |RESOLVED

 Resolution||FIXED

   Target Milestone|--- |4.6.0



--- Comment #6 from Andrew Pinski pinskia at gcc dot gnu.org 2013-02-07 
21:23:22 UTC ---

Fixed so closing; 4.6.

[Bug other/44116] 64bit inodes for source code causes Value too large for defined data type (XFS,inode64)

[pinskia at gcc dot gnu.org]

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



--- Comment #7 from Andrew Pinski pinskia at gcc dot gnu.org 2013-02-07 
21:31:13 UTC ---

Fixed so closing; 4.6.x and above is only supported for fixing bugs now.

[Bug other/44116] 64bit inodes for source code causes Value too large for defined data type (XFS,inode64)

[kasparek at fit dot vutbr dot cz]

--- Comment #4 from kasparek at fit dot vutbr dot cz  2010-06-08 10:34 
---
Hello, is there any progress in this, may I help with something?


-- 

kasparek at fit dot vutbr dot cz changed:

   What|Removed |Added

Version|4.5.0   |4.4.5


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

[Bug other/44116] 64bit inodes for source code causes Value too large for defined data type (XFS,inode64)

[kasparek at fit dot vutbr dot cz]

--- Comment #3 from kasparek at fit dot vutbr dot cz  2010-05-14 06:50 
---
(In reply to comment #1)
 to get the cc1 command line.  Then use gdb --args cc1 cmdline to debug the
 compiler.  Getting a backtrace before the abort would be nice.


(gdb) bt
#0  open_file (file=0x8a64148) at
/usr/local/lib/gcc/i686-pc-linux-gnu/4.3.4/include-fixed/sys/stat.h:510
#1  0x0866d707 in _cpp_find_file (pfile=0x8a5bb80, fname=0xff8d636f
test-10356.c, start_dir=0x8a5bbf4, fake=0 '\0', angle_brackets=0)
at ../../libcpp/files.c:378
#2  0x0866e2cc in cpp_read_main_file (pfile=0x8a5bb80, fname=0xff8d636f
test-10356.c) at ../../libcpp/init.c:561
#3  0x080f94a1 in c_common_post_options (pfilename=0x8945fdc) at
../../gcc/c-opts.c:1197
#4  0x08339410 in toplev_main (argc=11, argv=0xff8d4874) at
../../gcc/toplev.c:1810
#5  0x08118cb2 in main (argc=Cannot access memory at address 0x100
) at ../../gcc/main.c:35


I belive the problematic stat is gcc/files.c:232 (gcc-4.5.0). Would it be
possible to add config option to enable LFS that may be disabled by default?


-- 


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

[Bug other/44116] 64bit inodes for source code causes Value too large for defined data type (XFS,inode64)

[pinskia at gcc dot gnu dot org]

-- 

pinskia at gcc dot gnu dot org changed:

   What|Removed |Added

   Severity|major   |normal
  Component|c   |other


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