[Bug demangler/106622] Bug report
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106622 --- Comment #2 from Jonathan Wakely --- Also please check whether this is a duplicate of Bug 104435, Bug 105115, Bug 106224, or Bug 106641.
[Bug demangler/106622] Bug report
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106622 --- Comment #1 from Jonathan Wakely --- Please provide a more useful title than "Bug report". Everything in bugzilla is a bug report.
[Bug demangler/106622] New: Bug report
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106622 Bug ID: 106622 Summary: Bug report Product: gcc Version: rust/master Status: UNCONFIRMED Severity: normal Priority: P3 Component: demangler Assignee: unassigned at gcc dot gnu.org Reporter: sophrosx at gmail dot com Target Milestone: --- Created attachment 53459 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53459=edit testcases for nm-new Hello, I detected the memory leak and dead loop problems through fuzz testing, which I think might be a vulnerability. I found that the binutils-gdb[https://github.com/bminor/binutils-gdb]'s program nm-new with the test inputs triggered dead loop and memory leak vulnerabilities. As a result, I submit the testcases to binutils and here is the bug report[https://sourceware.org/bugzilla/show_bug.cgi?id=29492]. The configuration of binutils is: $ ./configure --disable-shared && make -j and compiled with gcc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0 Then the maintainer Alan Modra[amo...@gmail.com] told me that the endless looping is all in the rust demangler. What is more, the symbols being demangled are: 1) _RYXBAL_OFFGLOBTABLE_ 2) _RYFGNUSLT_FHStNB10ay_start 3) _RYDGLOBOFFSET_TABLE_ 4) _RYFGDIC6gnu_compilediBtOhighlightEH_FRAME_HDR 5) _RYFUDGC6ShigdefaulttiBtOhighlightEH_FRAME_HDR 6) _RYFUDGC6Shighdignu_compiledhlightEH_FRAME_HDR 7) _RYFIMYeB_xDGLtSarray_start 8) _RYdMMYTopFinFGAarral_start 9) _RMYADGC0hdpnit_Grray_start 10) _RYNSMICu2FiFGtDBrray_s 11) _RYTOdPjesistePDGC1onRLab_e 12) _RIYADGO0Rdpnit_Grray_start Further more, I add those testcases in the attachment. If there is anything I am unclear about or need to discuss further, please feel free to contact me~ Looking forward to your reply!
[Bug d/103840] d: Errors message: Please submit a full bug report in testsuite
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103840 Andrew Pinski changed: What|Removed |Added Target Milestone|--- |12.0
[Bug d/103840] d: Errors message: Please submit a full bug report in testsuite
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103840 Iain Buclaw changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Iain Buclaw --- Fix committed.
[Bug d/103840] d: Errors message: Please submit a full bug report in testsuite
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103840 --- Comment #3 from CVS Commits --- The master branch has been updated by Iain Buclaw : https://gcc.gnu.org/g:c43b5909031c7aa32ac65df3e392a12d32c45194 commit r12-6185-gc43b5909031c7aa32ac65df3e392a12d32c45194 Author: Iain Buclaw Date: Sun Jan 2 13:36:51 2022 +0100 d: Merge upstream dmd 001bfd97b, druntime 759e6023, phobos 468788323. D front-end changes: - Import latest changes to mainline. - Fix bad format specifiers in front-end errors (PR103840). - Refactoring of some leaf modules to the dmd/root package. - Updating copyright notice dates and urls. Phobos changes: - Import latest changes to mainline. gcc/d/ChangeLog: PR d/103840 * dmd/MERGE: Merge upstream dmd 001bfd97b. * Make-lang.in (D_FRONTEND_OBJS): Rename d/complex.o to d/root-complex.o, and d/utf.o to d/root/utf.o. libphobos/ChangeLog: * libdruntime/MERGE: Merge upstream druntime 759e6023. * src/MERGE: Merge upstream phobos 468788323.
[Bug d/103840] d: Errors message: Please submit a full bug report in testsuite
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103840 --- Comment #2 from Iain Buclaw --- Fix in upstream. https://github.com/dlang/dmd/pull/13462
[Bug d/103840] d: Errors message: Please submit a full bug report in testsuite
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103840 --- Comment #1 from Iain Buclaw --- In both cases, the dmd front-end has an error with %zu as a format specifier in the message.
[Bug d/103840] New: d: Errors message: Please submit a full bug report in testsuite
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103840 Bug ID: 103840 Summary: d: Errors message: Please submit a full bug report in testsuite Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: d Assignee: ibuclaw at gdcproject dot org Reporter: ibuclaw at gdcproject dot org Target Milestone: --- A number of fail_compilation tests are silently passing with the error: Please submit a full bug report. They should all be fixed. --- 299.o fail_compilation/fail299.d^M ^M in pp_format, at pretty-print.c:1478^M 0x9db102 pp_format(pretty_printer*, text_info*)^M ../../gcc/pretty-print.c:1478^M 0x20ae97c diagnostic_report_diagnostic(diagnostic_context*, diagnostic_info*)^M ../../gcc/diagnostic.c:1346^M 0xbe43aa d_diagnostic_report_diagnostic^M ../../gcc/d/d-diagnostic.cc:203^M 0xbe450c verror(Loc const&, char const*, __va_list_tag*, char const*, char const*, char const*)^M ../../gcc/d/d-diagnostic.cc:242^M 0xab2769 error(Loc const&, char const*, ...)^M ../../gcc/d/dmd/errors.d:100^M 0xacdf78 _D3dmd13expressionsem3fitFCQz7dstruct17StructDeclarationKxSQCf7globals3LocPSQCw6dscope5ScopePSQDo4root5array__T5ArrayTCQEn10expression10ExpressionZQBkCQFt5mtype4TypeZb^M ../../gcc/d/dmd/expressionsem.d:13111^M --- fail_compilation/fail1995.d:12:24: note: Path(s) searched (as provided by '-J'):^M ^M in pp_format, at pretty-print.c:1478^M 0x9db102 pp_format(pretty_printer*, text_info*)^M ../../gcc/pretty-print.c:1478^M 0x20ae97c diagnostic_report_diagnostic(diagnostic_context*, diagnostic_info*)^M ../../gcc/diagnostic.c:1346^M 0xbe43aa d_diagnostic_report_diagnostic^M ../../gcc/d/d-diagnostic.cc:203^M 0xaba431 Expression::errorSupplemental(char const*, ...)^M ../../gcc/d/dmd/expression.d:815^M ---
[Bug c++/79736] [5 Regression] Please submit a full bug report: unable to create precompiled headers
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79736 Andrew Pinski changed: What|Removed |Added Status|WAITING |RESOLVED Resolution|--- |FIXED --- Comment #4 from Andrew Pinski --- Closing as fixed.
[Bug c++/79736] [5 Regression] Please submit a full bug report: unable to create precompiled headers
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79736 Jonathan Wakely changed: What|Removed |Added Keywords||ice-on-valid-code Known to work||4.9.4, 6.1.0 Target Milestone|--- |6.0 Summary|Please submit a full bug|[5 Regression] Please |report: unable to create|submit a full bug report: |precompiled headers |unable to create ||precompiled headers Known to fail||5.1.0, 5.5.0 --- Comment #3 from Jonathan Wakely --- I can reproduce this with gcc 5 but not gcc 6 or later. The preprocessed source is 800kB even compressed, so I can't attach it. The ICE started with r221641 PR c++/65498 * pt.c (get_mostly_instantiated_function_type): Just return the type of the partially instantiated template in DECL_TI_TEMPLATE. It was fixed by r227846 2015-09-17 Richard Biener * cp-tree.h (note_decl_for_pch): Remove. * class.c (build_clone): Do not call note_decl_for_pch. * semantics.c (finish_member_declaration): Likewise. (note_decl_for_pch): Remove. * decl2.c (c_parse_final_cleanups): Mangle all globals before writing the PCH. Should we close it as FIXED?
Bug Report Duplication Problem - Help !
I've invited you to fill out the following form: Professional Profile To fill it out, visit: https://docs.google.com/forms/d/e/1FAIpQLSfQTZkrylE1t49gjzewPQSPWHFnPtGCZfRujg_G8VTwqGrbHg/viewform?c=0w=1usp=mail_form_link Dear friend, I am a masters student in Computer Science at the Federal University of Bahia, Salvador, Brazil, under the advising of Dr. Eduardo Almeida. We chose you because you participated in one of the open source projects included in this study. All the information provided will be kept confidential. We have no intention to judge your work since we are merely interested in learning about some aspects of your work. We are investigating the bug report duplication problem, so based on your experience using bug-trackers, we would like to invite you to participate in a short 8-10 minute survey that our research group is conducting to get opinion about this subject. Please, return it until April 15th, 2018. We will offer a lottery ticket to compete for an Amazon $100 credit and the results of the study when we finished the analysis. We appreciate your time! Best Regards, Alexandre Gitirana Google Forms: Create and analyze surveys.
[Survey Invite] Bug report duplication problem - Help our study
I've invited you to fill out the following form: Professional Profile To fill it out, visit: https://docs.google.com/forms/d/e/1FAIpQLSfQTZkrylE1t49gjzewPQSPWHFnPtGCZfRujg_G8VTwqGrbHg/viewform?c=0w=1usp=mail_form_link Dear friend, I am a masters student in Computer Science at the Federal University of Bahia, Salvador, Brazil, under the advising of Dr. Eduardo Almeida. We chose you because you participated in one of the open source projects included in this study. All the information provided will be kept confidential. We have no intention to judge your work since we are merely interested in learning about some aspects of your work. We are investigating the bug report duplication problem, so based on your experience using bug-trackers, we would like to invite you to participate in a short 8-10 minute survey that our research group is conducting to get opinion about this subject. Please, return it until March 31st, 2018. We will offer a lottery ticket to compete for an Amazon $100 credit and the results of the study when we finished the analysis. We appreciate your time! Best Regards, Alexandre Gitirana Google Forms: Create and analyze surveys.
[Bug c++/79736] Please submit a full bug report: unable to create precompiled headers
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79736 --- Comment #2 from x800 --- Hello, do you mean this sequence: g++ -E hdr.h -o hdr2.h g++ -fpreprocessed hdr2.h ? The same result.
[Bug c++/79736] Please submit a full bug report: unable to create precompiled headers
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79736 Richard Biener changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed||2017-02-28 Ever confirmed|0 |1 --- Comment #1 from Richard Biener --- Please provide a testcase. Does it reproduce if you first preprocess hdr.h and then create the PCH?
[Bug c++/79736] New: Please submit a full bug report: unable to create precompiled headers
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79736 Bug ID: 79736 Summary: Please submit a full bug report: unable to create precompiled headers Product: gcc Version: 5.4.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: x800x800 at email dot cz Target Milestone: --- g++ is unable to precompile header file from PCL library. The eader file hdr.h contains only one line to reproduce problem: "#include " and command is "g++ -I /opt/pcl/pcl-1.8/include/pcl-1.8/ -I /usr/include/eigen3/ -I /usr/include/vtk-5.10/ hdr.h". Compiler is g++ 5.4 in the Ubuntu 16.04, PCL library 1.8 and 1.7 has the same problem. The full compiler output is: In file included from /usr/include/eigen3/Eigen/Geometry:44:0, from /opt/pcl/include/pcl-1.8/pcl/correspondence.h:47, from /opt/pcl/include/pcl-1.8/pcl/visualization/pcl_visualizer.h:42, from stdafx.h:10: /usr/include/eigen3/Eigen/src/Geometry/Transform.h: In instantiation of ‘Eigen::Transform<Scalar, Dim, Mode, _Options>::Transform(const Eigen::Transform<_Scalar, Dim, Mode, OtherOptions>&) [with int OtherOptions = 0; _Scalar = float; int _Dim = 3; int _Mode = 2; int _Options = 0]’: /usr/include/eigen3/Eigen/src/Geometry/Transform.h:312:10: required by substitution of ‘template Eigen::Transform<Scalar, Dim, Mode, _Options>::Transform(const Eigen::Transform<_Scalar, Dim, Mode, OtherOptions>&) [with int OtherOptions = 0]’ /opt/pcl/include/pcl-1.8/pcl/common/eigen.h:354:14: required from here /usr/include/eigen3/Eigen/src/Geometry/Transform.h:312:10: internal compiler error: Segmentation fault inline Transform(const Transform<Scalar,Dim,Mode,OtherOptions>& other) ^ Please submit a full bug report, with preprocessed source if appropriate. See for instructions.
[Bug c++/55287] GCC crashes and asks to file bug report
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55287 --- Comment #4 from Gordon Cichon gordoncichon at gmail dot com 2012-11-13 08:33:01 UTC --- Why is GCC comsuming so much memory? The program has 6.4MB source code, it is a single function. All optimizations are turned off. And there is 2GB memory in the system. Well, shouldn't it be possible to compile this program?
[Bug c++/55287] GCC crashes and asks to file bug report
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55287 --- Comment #5 from Jonathan Wakely redi at gcc dot gnu.org 2012-11-13 09:44:26 UTC --- 6.4MB in a single function is the problem. The compiler has to process that entire function at once. And 2GB is not a great amount.
[Bug c++/55287] GCC crashes and asks to file bug report
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55287 Manuel López-Ibáñez manu at gcc dot gnu.org changed: What|Removed |Added CC||manu at gcc dot gnu.org --- Comment #6 from Manuel López-Ibáñez manu at gcc dot gnu.org 2012-11-13 11:59:48 UTC --- (In reply to comment #4) Why is GCC comsuming so much memory? The program has 6.4MB source code, it is a single function. All optimizations are turned off. And there is 2GB memory in the system. Well, shouldn't it be possible to compile this program? That depends on the program, where the memory goes, possible bugs, etc. To start investigating this, GCC devs would need the info requested here: http://gcc.gnu.org/bugs/#report That said, even if you provided that info, it is unlikely that anyone will look into this bug, since it is a unusual case. If adding 2 or 4 more GBs of memory (or splitting the function into many small pieces) solves the issue, then it is simpler to just do that, and focus on fixing other bugs. Of course, nothing prevents you from investigating the issue yourself. Perhaps you are able to uncover a clear bug, memory leak or potential improvement. See: http://gcc.gnu.org/wiki/Speedup_areas http://gcc.gnu.org/wiki/Memory_management http://gcc.gnu.org/wiki/PerformanceTesting
[Bug c++/55287] New: GCC crashes and asks to file bug report
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55287 Bug #: 55287 Summary: GCC crashes and asks to file bug report Classification: Unclassified Product: gcc Version: 4.4.5 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassig...@gcc.gnu.org ReportedBy: gordoncic...@gmail.com This is a compiler bug that occurs on Debian squeeze.. uname -a Linux caraway 2.6.32-5-686 #1 SMP Sun Sep 23 09:49:36 UTC 2012 i686 GNU/Linux gcc -v Using built-in specs. Target: i486-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Debian 4.4.5-8' --with-bugurl=file:///usr/share/doc/gcc-4.4/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.4 --enable-shared --enable-multiarch --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.4 --libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-targets=all --with-arch-32=i586 --with-tune=generic --enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu Thread model: posix gcc version 4.4.5 (Debian 4.4.5-8) g++ -save-temps -c -o gcc-bug.o gcc-bug.cc g++: Internal error: Killed (program cc1plus) Please submit a full bug report. See file:///usr/share/doc/gcc-4.4/README.Bugs for instructions.
[Bug c++/55287] GCC crashes and asks to file bug report
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55287 Paolo Carlini paolo.carlini at oracle dot com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||INVALID --- Comment #1 from Paolo Carlini paolo.carlini at oracle dot com 2012-11-12 15:22:25 UTC --- gcc4.4.x is not maintained anymore. Please try again with a GCC from a currently maintained branch and in case file a proper report: http://gcc.gnu.org/bugs/#report
[Bug c++/55287] GCC crashes and asks to file bug report
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55287 --- Comment #2 from Andrew Pinski pinskia at gcc dot gnu.org 2012-11-12 17:01:57 UTC --- Also this ICE is really the kernel killing the program as it ran out of memory or it was over one of the ulimits. Most likely ran of memory.
[Bug c++/55287] GCC crashes and asks to file bug report
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55287 --- Comment #3 from Paolo Carlini paolo.carlini at oracle dot com 2012-11-12 17:50:20 UTC --- Indeed.
[Bug c/55084] please submit full bug report
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55084 Marek Polacek mpolacek at gcc dot gnu.org changed: What|Removed |Added Status|WAITING |RESOLVED Resolution||INVALID --- Comment #2 from Marek Polacek mpolacek at gcc dot gnu.org 2012-10-28 07:51:55 UTC --- Closing.
[Bug c/55084] New: please submit full bug report
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55084 Bug #: 55084 Summary: please submit full bug report Classification: Unclassified Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassig...@gcc.gnu.org ReportedBy: nikhildagade...@gmail.com internal error:Segmentation faultprogram cc1
[Bug c/55084] please submit full bug report
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55084 Marek Polacek mpolacek at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed||2012-10-26 CC||mpolacek at gcc dot gnu.org Ever Confirmed|0 |1 --- Comment #1 from Marek Polacek mpolacek at gcc dot gnu.org 2012-10-26 15:15:50 UTC --- Please read http://gcc.gnu.org/bugs/#report.
[Bug fortran/42848] compiler crashes and asks for this bug report
--- Comment #7 from fxcoudert at gcc dot gnu dot org 2010-09-10 21:08 --- Closing, please reopen with additional information if the problem persists with a more recent version of the compiler (= 4.5.0). Thanks! -- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added Status|WAITING |RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42848
[Bug fortran/42848] compiler crashes and asks for this bug report
--- Comment #6 from dfranke at gcc dot gnu dot org 2010-04-30 22:13 --- (In reply to comment #5) The compiler shouldn't crash anyway. But with a new version this problem should be solved too, isn't it? It should be. 4.5.0 was released by now. Could you check again? -- dfranke at gcc dot gnu dot org changed: What|Removed |Added CC||dfranke at gcc dot gnu dot ||org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42848
[Bug fortran/42848] compiler crashes and asks for this bug report
--- Comment #4 from burnus at gcc dot gnu dot org 2010-01-25 08:30 --- (In reply to comment #3) Today I am not able to reproduce the error. The compiler is working. Where exactly does the file m.mod reside? In the user directory or in a compiler directory? By default in the current directory - unless you used the option -Jdirectory to specify a different one. Note: In order to help writing makefiles which have dependencies on the .mod files, gfortran only overwrites the .mod files if they have changed. Thus, to reproduce the problem, you could compile the program with a different compiler or an older version of GCC - or simply create in any editor the .mod file. (Modifying the Fortran module + running gfortran also produces a new .mod file, but I think works also without the patch of PR 40195.) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42848
[Bug fortran/42848] compiler crashes and asks for this bug report
--- Comment #5 from frank dot braun at rz dot uni-regensburg dot de 2010-01-25 08:36 --- 've got it. Modifying the .mod file by hand makes the compiler crash. Deleting it lets it work correctly. The compiler shouldn't crash anyway. But with a new version this problem should be solved too, isn't it? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42848
[Bug fortran/42848] compiler crashes and asks for this bug report
--- Comment #3 from frank dot braun at rz dot uni-regensburg dot de 2010-01-25 07:57 --- Today I am not able to reproduce the error. The compiler is working. Where exactly does the file m.mod reside? In the user directory or in a compiler directory? Frank Braun (In reply to comment #2) Tobias, If we ask a bug submitter for more information, or to confirm our suspicions, we put the bug report in WAITING. Note to submitter: bug reports with status WAITING will be closed if not replied to within 3 months. Kind regards. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42848
[Bug fortran/42848] compiler crashes and asks for this bug report
--- Comment #2 from toon at moene dot org 2010-01-23 13:24 --- Tobias, If we ask a bug submitter for more information, or to confirm our suspicions, we put the bug report in WAITING. Note to submitter: bug reports with status WAITING will be closed if not replied to within 3 months. Kind regards. -- toon at moene dot org changed: What|Removed |Added Status|UNCONFIRMED |WAITING http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42848
[Bug fortran/42848] New: compiler crashes and asks for this bug report
Compiling a file with -c option (no exec)with gfortran lets the compiler output an internal error message. The file: ! Demoprogramm: ! Aufrufen einer C-Routine von Fortran aus ! Die C-Routine wird innerhalb eines Modules deklariert module cproc interface ! definierte Schnittstelle subroutine pythagoras (a, b, res) !DEC$ ATTRIBUTES C :: pythagoras !DEC$ ATTRIBUTES REFERENCE :: res real :: a, b, res end subroutine end interface end module program fmain use cproc implicit none real :: x, y, z write(*,*) ' Berechnung der Hypotenusenlaenge eines rechtwickligen Dreie cks' write(*,*) ' Geben Sie die beiden Seitenlaengen ein, die den rechten Win kel' write(*,*) ' einschliessen:' read(*,*) x, y call pythagoras(x,y,z) write(*,*) ' Die Laenge der Hypotenuse betraegt: ', z end program fmain The error message (translated by hand to english): administra...@pc6 /c/vectra/fortran $ gfortran -c fmain.f90 Unrecoverable error: Can't delete module file 'cproc.mod': Permission denied gfortran.exe: Onternal error: Aborted (program f951) Please send a complete error report in english ... administra...@pc6 /c/vectra/fortran $ gfortran -v Target: mingw32 Configured with: ../gcc-4.4.0/configure --enable-languages=c,ada,c++,fortran,ja va,objc,obj-c++ --disable-sjlj-exceptions --enable-shared --enable-libgcj --enab le-libgomp --with-dwarf2 --disable-win32-registry --enable-libstdcxx-debug --ena ble-version-specific-runtime-libs --prefix=/mingw --with-gmp=/mingw/src/gmp/root --with-mpfr=/mingw/src/mpfr/root --build=mingw32 Thread-Modell: win32 gcc-Version 4.4.0 (GCC) administra...@pc6 /c/vectra/fortran The error message (original as it appeared on the screen): administra...@pc6 /c/vectra/fortran $ gfortran -c fmain.f90 Schwerwiegender Fehler: Can't delete module file 'cproc.mod': Permission denied gfortran.exe: Interner Fehler: Aborted (Programm f951) Bitte senden Sie einen vollst#9500;ñndigen Fehlerbericht auf Englisch ein; Fehler in der deutschen #9500;£bersetzung sind an translation-team...@lists.sourceforge.net zu melden. Gehen Sie gem#9500;ñ#9500; den Hinweisen in http://gcc.gnu.org/bugs.html vor. administra...@pc6 /c/vectra/fortran $ gfortran -v Es werden eingebaute Spezifikationen verwendet. Ziel: mingw32 Konfiguriert mit: ../gcc-4.4.0/configure --enable-languages=c,ada,c++,fortran,ja va,objc,obj-c++ --disable-sjlj-exceptions --enable-shared --enable-libgcj --enab le-libgomp --with-dwarf2 --disable-win32-registry --enable-libstdcxx-debug --ena ble-version-specific-runtime-libs --prefix=/mingw --with-gmp=/mingw/src/gmp/root --with-mpfr=/mingw/src/mpfr/root --build=mingw32 Thread-Modell: win32 gcc-Version 4.4.0 (GCC) administra...@pc6 /c/vectra/fortran -- Summary: compiler crashes and asks for this bug report Product: gcc Version: 4.4.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: frank dot braun at rz dot uni-regensburg dot de GCC build triplet: MSYS full with gcc g++ and gfortran GCC host triplet: Dell Intel Windows Mingwin MSYS GCC target triplet: Dell Intel Windows Mingwin MSYS http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42848
[Bug fortran/42848] compiler crashes and asks for this bug report
--- Comment #1 from burnus at gcc dot gnu dot org 2010-01-22 17:44 --- Thanks for the bug report. However, I think this a duplicate of PR 40195 which was fixed 2009-05-22. Thus, the solution is to use any GCC 4.4.x or 4.5.x newer than 22 May 2009 such as 4.4.1, 4.4.2, or 4.4.3 - or a recent 4.5 experimental version. Comment from the other bug report: If a module file m.mod already exist, we look into it to check if it's ours; if not, we delete it and write ours. The problem is that the code doing that actually unlinks the file before closing it, which is not allowed on Windows Thus, a work around is to delete the *.mod file(s) manually before instructing gfortran to (over)write it. -- burnus at gcc dot gnu dot org changed: What|Removed |Added Summary|compiler crashes and asks |compiler crashes and asks |for this bug report |for this bug report http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42848
[Bug c/31886] (different from bug report c/31077 and 29241) C handling of always_inline attribute error and a solution
--- Comment #11 from rob1weld at aol dot com 2009-01-13 22:10 --- ping -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31886
[Bug c/31886] (different from bug report c/31077 and 29241) C handling of always_inline attribute error and a solution
--- Comment #12 from rguenth at gcc dot gnu dot org 2009-01-13 22:41 --- Fixed for GCC 4.4 (with unit-at-a-time being always on). -- rguenth at gcc dot gnu dot org changed: What|Removed |Added Status|NEW |RESOLVED Known to fail||3.4.6 4.1.2 4.3.2 Known to work||4.4.0 Resolution||FIXED Target Milestone|--- |4.4.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31886
[Bug c/38521] -masm=intel, struct output for __asm__() block causes gcc to ask for bug report.
--- Comment #1 from ubizjak at gmail dot com 2008-12-14 11:18 ---
There were many problems with -masm=intel, that were fixed for gcc-4.3 and
later by [1] and (many) followup patches. The change that you are looking for
is (gcc/config/i386/i386.c):
@@ -9037,8 +9047,9 @@ print_operand (FILE *file, rtx x, int co
else if (MEM_P (x))
{
- /* No `byte ptr' prefix for call instructions. */
- if (ASSEMBLER_DIALECT == ASM_INTEL code != 'X' code != 'P')
+ /* No `byte ptr' prefix for call instructions or BLKmode operands. */
+ if (ASSEMBLER_DIALECT == ASM_INTEL code != 'X' code != 'P'
+ GET_MODE (x) != BLKmode)
{
const char * size;
switch (GET_MODE_SIZE (GET_MODE (x)))
However, this is just one of many changes to properly support -masm=intel, so
my best advice is to use gcc-4.3.x. This won't be fixed for gcc-4.2.
[1] http://gcc.gnu.org/ml/gcc-patches/2007-10/msg01254.html
--
ubizjak at gmail dot com changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Known to work||4.3.0
Resolution||WONTFIX
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38521
[Bug c/38521] New: -masm=intel, struct output for __asm__() block causes gcc to ask for bug report.
I'm currently writing a small kernel, and gcc asked me to file a bug report.
I've scrapped the file from anything not directly related to the bug, which
makes it quite small.
I'm aware the assembly syntax is most likely wrong.
Hope this is useful.
Command line :
##
gcc -v -save-temps -nostdinc -masm=intel -Wall interrupt.c
Output :
Utilisation des specs internes.
Cible : i486-linux-gnu
Configuré avec: ../src/configure -v
--enable-languages=c,c++,fortran,objc,obj-c++,treelang --prefix=/usr
--enable-shared --with-system-zlib --libexecdir=/usr/lib
--without-included-gettext --enable-threads=posix --enable-nls
--with-gxx-include-dir=/usr/include/c++/4.2 --program-suffix=-4.2
--enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-mpfr
--enable-targets=all --enable-checking=release --build=i486-linux-gnu
--host=i486-linux-gnu --target=i486-linux-gnu
Modèle de thread: posix
version gcc 4.2.4 (Ubuntu 4.2.4-1ubuntu3)
/usr/lib/gcc/i486-linux-gnu/4.2.4/cc1 -E -quiet -nostdinc -v interrupt.c
-masm=intel -mtune=generic -Wall -fpch-preprocess -o interrupt.i
la recherche pour #include ... débute ici :
la recherche pour #include ... débute ici:
Fin de la liste de recherche.
/usr/lib/gcc/i486-linux-gnu/4.2.4/cc1 -fpreprocessed interrupt.i -quiet
-dumpbase interrupt.c -masm=intel -mtune=generic -auxbase interrupt -Wall
-version -fstack-protector -fstack-protector -o interrupt.s
GNU C version 4.2.4 (Ubuntu 4.2.4-1ubuntu3) (i486-linux-gnu)
compiled by GNU C version 4.2.4 (Ubuntu 4.2.4-1ubuntu3).
heuristiques GGC: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
Compiler executable checksum: e2971cf2189271aeeb10133511ecea3a
interrupt.c: Dans la fonction «f» :
interrupt.c:5: erreur interne du compilateur: dans print_operand, à
config/i386/i386.c:7961
Veuillez soumettre un rapport complet d'anomalies,
avec le source pré-traité si nécessaire.
Consultez URL:http://gcc.gnu.org/bugs.html pour plus de détail.
For Debian GNU/Linux specific bug reporting instructions,
see URL:file:///usr/share/doc/gcc-4.2/README.Bugs.
source code :
#
--- interrupt.c -
struct{}i;
void f() {
__asm__(sidt %0\n
: =m (i));
}
-
--
Summary: -masm=intel, struct output for __asm__() block causes
gcc to ask for bug report.
Product: gcc
Version: 4.2.4
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: vbernetr at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38521
Worth a bug report?
Hello,
I ran into the following using gcc 4.2.3 on ubuntu 8.04. I ran it with
-Werror so it died on receiving this warning:
cc1: warnings being treated as errors
tux3fuse.c: In function 'tux3_lookup':
tux3fuse.c:78: warning: initialized field overwritten
tux3fuse.c:78: warning: (near initialization for 'ep.attr')
tux3fuse.c:79: warning: initialized field overwritten
tux3fuse.c:79: warning: (near initialization for 'ep.attr')
tux3fuse.c:80: warning: initialized field overwritten
tux3fuse.c:80: warning: (near initialization for 'ep.attr')
tux3fuse.c:81: warning: initialized field overwritten
tux3fuse.c:81: warning: (near initialization for 'ep.attr')
tux3fuse.c:82: warning: initialized field overwritten
tux3fuse.c:82: warning: (near initialization for 'ep.attr')
tux3fuse.c:83: warning: initialized field overwritten
tux3fuse.c:83: warning: (near initialization for 'ep.attr')
tux3fuse.c:85: warning: initialized field overwritten
tux3fuse.c:85: warning: (near initialization for 'ep.attr')
the code:
struct fuse_entry_param ep = {
.attr.st_mode = inode-i_mode,
.attr.st_atime = inode-i_atime,
.attr.st_mtime = inode-i_mtime,
.attr.st_ctime = inode-i_ctime,
.attr.st_size = inode-i_size,
.attr.st_uid = inode-i_uid,
.attr.st_gid = inode-i_gid,
.attr.st_nlink = inode-i_links,
.ino = (fuse_ino_t)inode,
.generation = 1,
.attr_timeout = 1.0,
.entry_timeout = 1.0,
};
It worked fine when i changed the code as .attr = { .st_mode = ...}
Thanks,
--
Pranith.
Bug report
gcc --v Using built-in specs. Target: i486-linux-gnu Configured with: ../src/configure -v --enable-languages=c,c++,fortran,objc,obj-c++,treelang --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.2 --program-suffix=-4.2 --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-mpfr --enable-targets=all --enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu Thread model: posix gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7) Distro: Ubuntu 8.04 Commands: sudo apt-get remove wine sudo apt-get install git-core git clone git://source.winehq.org/git/wine.git ~/wine-git sudo apt-get build-dep wine sudo apt-get install fakeroot cd ~/wine-git ./configure --prefix=/usr make Errors: make[2]: Siirrytään hakemistoon /home/sla/wine-git/dlls/urlmon gcc -c -I. -I. -I../../include -I../../include -D__WINESRC__ -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wwrite-strings -Wpointer-arith -g -O2 -o bindctx.o bindctx.c gcc -c -I. -I. -I../../include -I../../include -D__WINESRC__ -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wwrite-strings -Wpointer-arith -g -O2 -o binding.o binding.c gcc -c -I. -I. -I../../include -I../../include -D__WINESRC__ -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wwrite-strings -Wpointer-arith -g -O2 -o bindprot.o bindprot.c gcc -c -I. -I. -I../../include -I../../include -D__WINESRC__ -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wwrite-strings -Wpointer-arith -g -O2 -o download.o download.c gcc -c -I. -I. -I../../include -I../../include -D__WINESRC__ -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wwrite-strings -Wpointer-arith -g -O2 -o file.o file.c file.c: In function #8216;FileProtocol_Start#8217;: file.c:187: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See URL:http://gcc.gnu.org/bugs.html for instructions. -- file.c Description: Binary data
[Bug fortran/36465] New: Compilation crashes and asks me to submit a bug report
There is a simulation code that I am trying to make run faster by trying several compile optimization flags. It also uses OpenMP to utilize multiple cores. Today I got this: Driving: /home/nimar/opt/gcc-4.3.0/bin/gfortran -v -save-temps -I/home/nimar/opt/gcc-4.3.0/include -O3 -fimplicit-none -fopenmp -ftree-parallelize-loops=4 -funroll-all-loops -msse4a -march=native -fipa-pta -fipa-cp -funroll-loops -fprefetch-loop-arrays -funit-at-a-time -combine Bed_ini.f -lgfortranbegin -lgfortran -lm -shared-libgcc Using built-in specs. Target: i686-pc-linux-gnu Configured with: /home/nimar/build/gcc-4.3.0/configure --prefix=/home/nimar/opt/gcc-4.3.0 --with-gmp=/home/nimar/opt/gcc-4.3.0 --with-mpfr=/home/nimar/opt/gcc-4.3.0 --enable-languages=c,c++,fortran Thread model: posix gcc version 4.3.0 (GCC) COLLECT_GCC_OPTIONS='-v' '-save-temps' '-I/home/nimar/opt/gcc-4.3.0/include' '-O3' '-fimplicit-none' '-fopenmp' '-ftree-parallelize-loops=4' '-funroll-all-loops' '-msse4a' '-fipa-pta' '-fipa-cp' '-funroll-loops' '-fprefetch-loop-arrays' '-funit-at-a-time' '-combine' '-shared-libgcc' '-pthread' /home/nimar/opt/gcc-4.3.0/libexec/gcc/i686-pc-linux-gnu/4.3.0/f951 Bed_ini.f -ffixed-form -march=core2 -mcx16 -msahf --param l1-cache-size=32 --param l1-cache-line-size=64 -mtune=core2 -quiet -dumpbase Bed_ini.f -msse4a -auxbase Bed_ini -O3 -version -fimplicit-none -fopenmp -ftree-parallelize-loops=4 -funroll-all-loops -fipa-pta -fipa-cp -funroll-loops -fprefetch-loop-arrays -funit-at-a-time -I/home/nimar/opt/gcc-4.3.0/include -fintrinsic-modules-path /home/nimar/opt/gcc-4.3.0/lib/gcc/i686-pc-linux-gnu/4.3.0/finclude -o Bed_ini.s GNU F95 (GCC) version 4.3.0 (i686-pc-linux-gnu) compiled by GNU C version 4.3.0, GMP version 4.2.2, MPFR version 2.3.1. GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072 Bed_ini.f: In function pr9_bed: Bed_ini.f:206: internal compiler error: in get_smt_for, at tree-ssa-alias.c:3203 Please submit a full bug report, with preprocessed source if appropriate. See http://gcc.gnu.org/bugs.html for instructions. I use a Makefile, but I got the same when trying: /home/nimar/opt/gcc-4.3.0/bin/gfortran -v -save-temps -I/home/nimar/opt/gcc-4.3.0/include -O3 -fimplicit-none -fopenmp -ftree-parallelize-loops=4 -funroll-all-loops -msse4a -march=native -fipa-pta -fipa-cp -funroll-loops -fprefetch-loop-arrays -funit-at-a-time -combine Bed_ini.f I am running ubuntu 8.04, x86 on a core2quad, and I compiled gcc-4.3.0 myself (along with gmp and mpfr). I have never come across sth like that before, so please tell me If I need to submit sth more. I hope these help. -- Summary: Compilation crashes and asks me to submit a bug report Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: critical Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: pattakosn at yahoo dot com GCC build triplet: i686-pc-linux GCC host triplet: i686-pc-linux GCC target triplet: i686-pc-linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36465
[Bug fortran/36465] Compilation crashes and asks me to submit a bug report
--- Comment #1 from pattakosn at yahoo dot com 2008-06-08 12:05 --- Created an attachment (id=15729) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15729action=view) The source code and the generated .s file This is the source file that crashes and the .s file that is generated. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36465
[Bug middle-end/36465] Compilation crashes and asks me to submit a bug report
-- pinskia at gcc dot gnu dot org changed: What|Removed |Added CC||pinskia at gcc dot gnu dot ||org Severity|critical|normal Component|fortran |middle-end http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36465
[Bug middle-end/36465] Compilation crashes and asks me to submit a bug report
--- Comment #2 from pattakosn at yahoo dot com 2008-06-08 13:49 --- I downloaded and compiled 4.3.1 which seems to work well. However I also downloaded the latest snapshot (4.4-20080606) and I get an other bug : Using built-in specs. Target: i686-pc-linux-gnu Configured with: /home/nimar/build/2/gcc-4.4-20080606/configure --prefix=/home/nimar/opt/gcc-4.4-20080606 --with-gmp=/home/nimar/opt/gcc-4.4-20080606 --with-mpfr=/home/nimar/opt/gcc-4.4-20080606 --enable-languages=c,c++,fortran Thread model: posix gcc version 4.4.0 20080606 (experimental) (GCC) COLLECT_GCC_OPTIONS='-v' '-save-temps' '-I/home/nimar/opt/gcc-4.4-20080606/include' '-O3' '-fimplicit-none' '-fopenmp' '-ftree-parallelize-loops=4' '-funroll-all-loops' '-msse4a' '-fipa-pta' '-fipa-cp' '-funroll-loops' '-fprefetch-loop-arrays' '-funit-at-a-time' '-combine' '-c' '-pthread' /home/nimar/opt/gcc-4.4-20080606/libexec/gcc/i686-pc-linux-gnu/4.4.0/f951 main3.f -ffixed-form -march=core2 -mcx16 -msahf --param l1-cache-size=32 --param l1-cache-line-size=64 --param l2-cache-size=3072 -mtune=core2 -quiet -dumpbase main3.f -msse4a -auxbase main3 -O3 -version -fimplicit-none -fopenmp -ftree-parallelize-loops=4 -funroll-all-loops -fipa-pta -fipa-cp -funroll-loops -fprefetch-loop-arrays -funit-at-a-time -I/home/nimar/opt/gcc-4.4-20080606/include -fintrinsic-modules-path /home/nimar/opt/gcc-4.4-20080606/lib/gcc/i686-pc-linux-gnu/4.4.0/finclude -o main3.s GNU Fortran (GCC) version 4.4.0 20080606 (experimental) (i686-pc-linux-gnu) compiled by GNU C version 4.4.0 20080606 (experimental), GMP version 4.2.2, MPFR version 2.3.1. GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096 main3.f: In function MAIN__.omp_fn.0: main3.f:390: error: stmt (0xb7d02410) marked modified after optimization pass: omp_get_thread_num (); main3.f:390: internal compiler error: verify_ssa failed Please submit a full bug report, with preprocessed source if appropriate. See http://gcc.gnu.org/bugs.html for instructions. compile line was: /home/nimar/opt/gcc-4.4-20080606/bin/gfortran -v -save-temps -I/home/nimar/opt/gcc-4.4-20080606/include -O3 -fimplicit-none -fopenmp -ftree-parallelize-loops=4 -funroll-all-loops -msse4a -march=native -fipa-pta -fipa-cp -funroll-loops -fprefetch-loop-arrays -funit-at-a-time -combine main3.f -c The files i uploaded are no more relevant to this. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36465
[Bug middle-end/36465] Compilation crashes and asks me to submit a bug report
--- Comment #3 from pattakosn at yahoo dot com 2008-06-08 14:06 --- Created an attachment (id=15730) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15730action=view) the file that the latest gfortran (4.4-20080606) fails to compile and the produced .s file This is the file relevant to the second bug -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36465
[Bug middle-end/36465] Compilation crashes and asks me to submit a bug report
--- Comment #4 from pattakosn at yahoo dot com 2008-06-08 14:10 --- (In reply to comment #2) I downloaded and compiled 4.3.1 which seems to work well. I am sorry, maybe I was not clear. I meant that I downloaded and compiled 4.3.1 and 4.4-20080606 and then gfortran 4.3.1 compiles my source without any failures, and the produced executable seems to run correctly. The new bug regards the latest snapshot which fails to compile my source. The files I submitted first are no longer relevant. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36465
[Bug middle-end/36465] Compilation crashes and asks me to submit a bug report
--- Comment #5 from pinskia at gcc dot gnu dot org 2008-06-08 14:12 --- fipa-pta is known to be broken, don't use it. *** This bug has been marked as a duplicate of 29212 *** -- 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=36465
[Bug fortran/34837] New: gfortran crashes and asks for bug report
gfortran -c makeplot.f90
makeplot.f90: In function 'MAIN__':
makeplot.f90:103: internal compiler error: in expand_expr_addr_expr_1, at
expr.c:6517
Please submit a full bug report,
with preprocessed source if appropriate.
__
gfortran -v
Using built-in specs.
Target: i386-apple-darwin8
Configured with: ../gcc-4.2-20060610/configure --prefix=/sw
--prefix=/sw/lib/gcc4 --enable-languages=c,c++,fortran,objc,java --with-gmp=/sw
--with-included-gettext --host=i386-apple-darwin8
--with-as=/sw/lib/odcctools/bin/as --with-ld=/sw/lib/odcctools/bin/ld
--with-nm=/sw/lib/odcctools/bin/nm --mandir=/sw/lib/gcc4/share/man
--infodir=/sw/lib/gcc4/share/info --disable-multilib
Thread model: posix
gcc version 4.2.0 20060610 (experimental)
___
PROGRAM makeplot
!
! Take a lightcurve qdp file and try to configure a plot suitable
! for the WWW pages to be set up by Wayne
!
IMPLICIT NONE
!
INTEGER, PARAMETER :: max_val=4096, max_timescales = 10
CHARACTER*128:: cmdline
CHARACTER*64 :: filroot,outfil, label
INTEGER :: len
REAL*8, DIMENSION(max_val,max_timescales) :: day_no, day_err, rate,
rate_err, signif, weights
INTEGER :: nn(max_timescales)
INTEGER :: nts
CHARACTER*(128) :: line
INTEGER :: ios
INTEGER :: i, j, k, n
LOGICAL :: ok1, ok2
INTEGER :: j_use, count
REAL :: max_y
REAL :: wmean
!
!---
!
day_err = 1.0
rate_err = 1.0
CALL GETCL( cmdline )
len = LEN_TRIM(cmdline)
OPEN (1,FILE=cmdline,STATUS='old')
DO i = 1,3
READ (1,'(A)') line
END DO
j = 1
ok2 = .TRUE.
DO WHILE ( (j = max_timescales) .AND. (ok2) )
i = 1
ok1 = .TRUE.
DO WHILE ( ( i = max_val ) .AND. (ok1) )
READ (1,'(A)', IOSTAT = ios ) line
IF (ios == 0 ) THEN
IF (INDEX(LINE, ' no ') 0 ) THEN
ok1 = .FALSE.
! write (*,*) '1',trim(line)
ELSE
READ (line, *, IOSTAT = ios ) day_no(i,j), day_err(i,j),
rate(i,j), rate_err(i,j)
IF ( ios /= 0 ) THEN
ok1 = .FALSE.
!write (*,*) '2',trim(line)
ELSE
i = i + 1
END IF
END IF
ELSE
ok1 = .false.
IF ( ios 0 ) ok2 = .false.
END IF
END DO
IF ( i 1 ) THEN
nn(j) = i - 1
WRITE (*,*) j, ' Read ',nn(j), ' entries'
nts = j
j = j + 1
END IF
END DO
IF ( j max_timescales ) THEN
WRITE (*,*) ' Buffer overflow - too many timescales ', j
STOP
END IF
signif = rate / rate_err
weights = rate_err**-2.0
! find shortest timescale on which we have at least 4 points at 2 sigma
j_use = 5
DO j = nts, 1, -1
count = 0
n = nn(j)
DO i = 1, n
IF (signif(i,j) 2.0 ) count = count + 1
write (*,*) rate(i,j), rate_err(i,j), rate(i,j)/rate_err(i,j) ,
signif(i,j), count
END DO
write (*,*) j,count
IF (count =4 ) j_use = j
END DO
WRITE (*,*) 'Use ',j_use
i = INDEX(cmdline,'.qdp')
filroot = cmdline(1:i-1)
DO j = 1, nts
n = nn(j)
wmean = ( SUM( rate(1:n,j) * weights(1:n,j) ) / SUM(weights(1:n,j) ) )
WRITE (label,'(I4,A)') 2**2.0
OPEN (17, FILE='hdr.pco', STATUS='unknown')
OPEN (18, FILE='qdp.mod', STATUS='unknown')
WRITE (18,*) 'CONS'
WRITE (18,*) wmean, ' 0.0 0.0 0 ! 1 CO'
WRITE (17,*) 'SKIP SING'
WRITE (17,*) 'TIME OFF'
WRITE (17,'(2A)') 'MODEL @qdp.mod'
DO k = 1, nts
IF ( k /= j) WRITE (17,*) 'COL OFF ',i
END DO
WRITE (17,*) 'RX 1440 1750'
WRITE (17,*) 'LOC 0 0 1 1'
WRITE (17,*) 'LAB 1 LIN 90 0.019996 CEN Bot'
WRITE (17,*) 'LAB 1 POS 1461 0.0020009 Jan-1'
WRITE (17,*) 'LAB 2 LIN 90 0.019996 CEN Bot'
WRITE (17,*) 'LAB 2 POS 1551 0.0020009 Apr-1'
WRITE (17,*) 'LAB 3 LIN 90 0.019996 CEN Bot'
WRITE (17,*) 'LAB 3 POS 1642 0.0020009 Jul-1'
WRITE (17,*) 'LAB 4 LIN 90 0.019996 CEN Bot'
WRITE (17,*) 'LAB 4 POS 1734 0.0020009 Oct-1'
WRITE (17,*) 'LAB 5 LIN 0 0.050007 JUS Lef'
WRITE (17,*) 'LAB 5 POS 1730 0.0010005 1 mCrab'
WRITE (17,*) 'LAB F ',label, ' day bins'
WRITE (17,*) 'LAB T ', filroot
WRITE (17,*) 'LAB X Swift Days'
WRITE (17,*) 'LAB Y counts/s'
WRITE (17,*) 'RY -0.0004 0.0030003'
CLOSE (17)
CLOSE(18)
CALL SYSTEM ('qdp '//TRIM(cmdline)//' qdp.in')
CALL SYSTEM ('mv pgplot.ps '//TRIM(filroot)//TRIM(label)//'d.ps')
END DO
END PROGRAM makeplot
--
Summary: gfortran crashes and asks for bug report
Product: gcc
Version: 4.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned
[Bug fortran/34837] gfortran crashes and asks for bug report
--- Comment #1 from burnus at gcc dot gnu dot org 2008-01-17 22:45 --- Thanks for the bug report; however, I fail to reproduce the bug with either of 4.1.3, 4.2.2 and 4.3.0 on x86-64-linux. Your version 4.2.0 (experimental) is relatively old. (Even 4.1.3 might contain a bug fix, which was not in yet in 4.2.0.) Can you try with a newer version, for instance the one available from http://gcc.gnu.org/wiki/GFortranBinaries ? * * * The newest gfortran versions also have the following warning by default: weights = rate_err**-2.0 1 Warning: Extension: Unary operator following arithmetic operator (use parentheses) at (1) This is not only invalid Fortran but also not always well defined. What does the following mean: a**-b*c Does mean a**(-b) * c or a**(-b*c) - different compilers make different choices here. (In your case the choice is unambiguous but still not standard conform.) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34837
[Bug fortran/34837] gfortran crashes and asks for bug report
--- Comment #2 from skinner at milkyway dot gsfc dot nasa dot gov 2008-01-18 00:49 --- Subject: Re: gfortran crashes and asks for bug report burnus at gcc dot gnu dot org wrote: --- Comment #1 from burnus at gcc dot gnu dot org 2008-01-17 22:45 --- Thanks for the bug report; however, I fail to reproduce the bug with either of 4.1.3, 4.2.2 and 4.3.0 on x86-64-linux. Your version 4.2.0 (experimental) is relatively old. (Even 4.1.3 might contain a bug fix, which was not in yet in 4.2.0.) Can you try with a newer version, for instance the one available from http://gcc.gnu.org/wiki/GFortranBinaries ? * * * The newest gfortran versions also have the following warning by default: weights = rate_err**-2.0 1 Warning: Extension: Unary operator following arithmetic operator (use parentheses) at (1) This is not only invalid Fortran but also not always well defined. What does the following mean: a**-b*c Does mean a**(-b) * c or a**(-b*c) - different compilers make different choices here. (In your case the choice is unambiguous but still not standard conform.) Thanks for the v quick response I have installed gcc version 4.3.0 20071231 (experimental) [trunk revision 131236] (GCC) and the error goes away. I can turn it on and off by switching between the two, though it is not conclusive that the problem has been solved because it appeared to depend in some complex way on how the program was arranged, as if it was an overwriting/ buffer-overflow/memory leak sort of problem. So its disappearance could be a chance of how memory is allocated. Anyway my objective was to keep you informed - I had already found a fudge which allowed me to get the results I needed from the quick and dirty program. Incidentally the new version does indeed warn about **-2.0 . I agree it is bad practice but without looking carefully at the rules I am not sure that it is ungrammatical. -2.0 is after all a constant, so the expression is of the form [variable] [operator] [constant] Gerry -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34837
[Bug fortran/34837] gfortran crashes and asks for bug report
--- Comment #3 from kargl at gcc dot gnu dot org 2008-01-18 01:32 --- (In reply to comment #2) I have installed gcc version 4.3.0 20071231 (experimental) [trunk revision 131236] (GCC) and the error goes away. I can turn it on and off by switching between the two, though it is not conclusive that the problem has been solved because it appeared to depend in some complex way on how the program was arranged, as if it was an overwriting/ buffer-overflow/memory leak sort of problem. So its disappearance could be a chance of how memory is allocated. Add -Wall -fbounds-check to your command line. Fix all warnings and errors. Incidentally the new version does indeed warn about **-2.0 . I agree it is bad practice but without looking carefully at the rules I am not sure that it is ungrammatical. -2.0 is after all a constant, so the expression is of the form [variable] [operator] [constant] It doesn't matter. The ** operator has higher precedence than the - operator. In fact, you have [variable][operator][operator][constant]. You should also change the 2.0 to simply 2. Why? Because x**-2.0 may be to a function call of pow(x, -2.0) whereas x**2 becomes x*x. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34837
[Bug fortran/34837] gfortran crashes and asks for bug report
--- Comment #4 from pinskia at gcc dot gnu dot org 2008-01-18 02:24 --- WRITE (label,'(I4,A)') 2**2.0 This is what is crashing. I fixed this with PR 29982 over a year ago :). *** This bug has been marked as a duplicate of 29982 *** -- 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=34837
[Bug c/31886] (different from bug report c/31077 and 29241) C handling of always_inline attribute error and a solution
--- Comment #10 from rguenth at gcc dot gnu dot org 2007-08-20 07:58 --- Honza, can you look into this pls? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31886
[Bug c/31886] (different from bug report c/31077 and 29241) C handling of always_inline attribute error and a solution
--- Comment #8 from rob1weld at aol dot com 2007-08-06 06:44 --- GCC 4.2.2 20070804 is able to compile newer kernels as is 4.2.1 20070628. I guess 4.3 and 4.1 are the only series lacking this ability. I am not allowed to change the Summary: to add [4.3 Regression] to the begining since I did not create this report. If we desire to compile the Linux kernel with GCC 4.3 (and apparently, but not tested by me, GCC 4.1 also) we will need to fix this. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31886
[Bug c/31886] (different from bug report c/31077 and 29241) C handling of always_inline attribute error and a solution
--- Comment #9 from zhouyi04 at ios dot cn 2007-08-06 08:40 --- (In reply to comment #8) I try to compile my giving C program using gcc-4.2.1, the problem still exists. As my solution 1 suggests: a caller function is inlinable only if all of its callee functions are inlinable. while this is not the case in original tree-optimize.c (including that in CVS), which says a caller function should be inlined if one of its function is inlinable. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31886
[Bug c/31886] (different from bug report c/31077 and 29241) C handling of always_inline attribute error and a solution
--- Comment #7 from rob1weld at aol dot com 2007-08-02 17:24 --- Created an attachment (id=14010) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14010action=view) Example of kernel file that causes inlining failed error -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31886
[Bug c/31886] (different from bug report c/31077 and 29241) C handling of always_inline attribute error and a solution
--- Comment #6 from rob1weld at aol dot com 2007-08-02 17:18 --- I can confirm this too. Here is the bug report I was to post - but I searched to see if this was already reported ;) - Here are my notes: tree-inline.c - sorry, unimplemented: inlining failed ... function body not available When compiling the kernel with GCC version 4.3.0 20070630 or 20070716 it seems to remove (optimize away) functions which are needed. When GCC later discovers it needs the function afterall it crys function body not available and terminates the build with an error. This does not occur if I add -O0 on the end of the command line. :( I also do not have this problem when using GCC version 4.2.1 20070628 . http://www.kernel.org/pub/linux/kernel/v2.6/testing/linux-2.6.22-rc2.tar.bz2 make V=1 vmlinux ... /usr/test/bin/gcc -Wp,-MD,kernel/.futex.o.d -nostdinc -isystem /usr/test/lib/gcc/i686-pc-linux-gnu/4.3.0/include -D__KERNEL__ -Iinclude -Iinclude2 -Ilinux-2.6.22-rc2-source/include -include include/linux/autoconf.h -Ilinux-2.6.22-rc2-source/kernel -Ikernel -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -O2 -fprofile-arcs -ftest-coverage -D__arch_um__ -DSUBARCH=\i386\ -Ilinux-2.6.22-rc2-source/arch/um/include -Iarch/um/include -Ilinux-2.6.22-rc2-source/arch/um/include -Ilinux-2.6.22-rc2-source/arch/um/include/skas -Dvmap=kernel_vmap -Din6addr_loopback=kernel_in6addr_loopback -march=k8 -mpreferred-stack-boundary=2 -ffreestanding -D_LARGEFILE64_SOURCE -Derrno=kernel_errno -Dsigprocmask=kernel_sigprocmask -Dmktime=kernel_mktime -U__i386__ -Ui386 -fno-unit-at-a-time -fno-omit-frame-pointer -fno-optimize-sibling-calls -g -fno-stack-protector -Wdeclaration-after-statement -Wno-pointer-sign -DKBUILD_STR(s)=#s -DKBUILD_BASENAME=KBUILD_STR(futex) -DKBUILD_MODNAME=KBUILD_STR(futex) -c -o kernel/.tmp_futex.o linux-2.6.22-rc2-source/kernel/futex.c linux-2.6.22-rc2-source/kernel/futex.c: In function 'futex_requeue_pi': linux-2.6.22-rc2-source/kernel/futex.c:272: sorry, unimplemented: inlining failed in call to 'get_futex_key_refs': function body not available linux-2.6.22-rc2-source/kernel/futex.c:908: sorry, unimplemented: called from here make[2]: *** [kernel/futex.o] Error 1 make[1]: *** [kernel] Error 2 make: *** [vmlinux] Error 2 make: Leaving directory `linux-2.6.22-rc2-source' The message comes from this file: gcc-4_3-trunk/gcc/tree-inline.c , line 2443: sorry (inlining failed in call to %q+F: %s, fn, reason); sorry (called from here); and from here, /opt/gcc-4_3-trunk/gcc/diagnostic.def : DEFINE_DIAGNOSTIC_KIND (DK_SORRY, sorry, unimplemented: ) The same problem occurs when compiling these files: linux-2.6.22-rc2-source/mm/filemap.c linux-2.6.22-rc2-source/fs/buffer.c linux-2.6.22-rc2-source/fs/bio.c linux-2.6.22-rc2-source/fs/block_dev.c linux-2.6.22-rc2-source/fs/reiserfs/do_balan.c linux-2.6.22-rc2-source/fs/reiserfs/namei.c linux-2.6.22-rc2-source/fs/reiserfs/stree.c linux-2.6.22-rc2-source/block/elevator.c linux-2.6.22-rc2-source/block/ll_rw_blk.c linux-2.6.22-rc2-source/net/ipv4/ip_output.c linux-2.6.22-rc2-source/net/ipv4/igmp.c and linux-2.6.22-rc2-source/include/net/dst.h linux-2.6.22-rc2-source/net/ipv4/xfrm4_output.c and linux-2.6.22-rc2-source/include/net/dst.h linux-2.6.22-rc2-source/fs/udf/partition.c linux-2.6.22-rc2-source/net/ipv4/ipvs/ip_vs_xmit.c linux-2.6.22-rc2-source/net/ipv4/netfilter/nf_nat_rule.c linux-2.6.22-rc2-source/net/ipv6/ip6_output.c linux-2.6.22-rc2-source/net/ipv6/ip6_input.c linux-2.6.22-rc2-source/net/ipv6/ndisc.c linux-2.6.22-rc2-source/net/ipv6/mcast.c I tried this line in the kernel Makefile but still got the same error message: CFLAGS_futex.o += $(call cc-ifversion, -ge, 0403, -fno-inline) I would have preferred if that had worked rather than resorting to -O0 since there are so many files affected by this issue. I worked around this problem by editing linux-2.6.22-rc2-source/kernel/Makefile (and all the other makefiles) by adding this sort of line near the top of the Makefile: CFLAGS_futex.o += $(call cc-ifversion, -ge, 0403, -O0) That allows the kernel to build with GCC 4.3 but does not fix GCC itself. Here is the minimum command line to trigger the problem: gcc -O1 -fno-unit-at-a-time -c -o futex.o futex.i linux-2.6.22-rc2-source/kernel/futex.c: In function 'futex_requeue_pi': linux-2.6.22-rc2-source/kernel/futex.c:272: sorry, unimplemented: inlining failed in call to 'get_futex_key_refs': function body not available linux-2.6.22-rc2-source/kernel/futex.c:908: sorry, unimplemented: called from here If I use -O0 or leave off -fno-unit-at-a-time I don't get the error. These options are what are present in the kernel's makefile (not my preferences). The kernel's makefiles are written in a particular way to allow various other features to work (so a full overhaul of the all makefiles is out (for me)). If this is not a problem with GCC 4.3 but instead an issue with the way Linux was written then we
[Bug c/31886] (different from bug report c/31077 and 29241) C handling of always_inline attribute error and a solution
--- Comment #5 from rguenth at gcc dot gnu dot org 2007-05-10 11:04 --- Confirmed. Either we should not accept always_inline on a function not declared inline (or warn in that case), or a function marked always_inline should be considered for inlining always. Second, the t.i:3: sorry, unimplemented: inlining failed in call to 'alloc_null_binding1': function body not available is fixed in 4.1.2. Which leaves us with t.i:3: sorry, unimplemented: inlining failed in call to 'alloc_null_binding1': function not inlinable with the function not marked inline (but only for -O0, not -O). I guess we want to make that behavior at least consistent. Note with -O0 -finline we get t.i:3: sorry, unimplemented: inlining failed in call to 'alloc_null_binding1': function body not available again ;) -- rguenth at gcc dot gnu dot org changed: What|Removed |Added CC||rguenth at gcc dot gnu dot ||org, hubicka at gcc dot gnu ||dot org Status|WAITING |NEW Ever Confirmed|0 |1 Last reconfirmed|-00-00 00:00:00 |2007-05-10 11:04:34 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31886
[Bug c/31886] New: (different from bug report c/31077 and 29241) C handling of always_inline attribute error and a solution
When compiling following code with no optimize flags given, gcc will complain:
1 __attribute__((always_inline)) unsigned int
2 alloc_null_binding1(void)
3 {
4 return 1;
5 }
6
7 static inline __attribute__((always_inline)) int
ip_nat_initialized1(void)
8 {
9
10return 2;
11 }
12
13 int ip_nat_rule_find1(void)
14 {
15 int ret;
16 if (!ip_nat_initialized1()){
17ret = alloc_null_binding1();
18 }
19 return ret;
20 }
/***
***/
[EMAIL PROTECTED] inline]gcc -S hello.c
hello.c: In function 'ip_nat_rule_find1':
hello.c:3: sorry, unimplemented: inlining failed in call to
'alloc_null_binding1': function body not available
hello.c:17: sorry, unimplemented: called from here
/***
***/
solutions:
Solution 1:
--- gcc-4.1.0/gcc/tree-optimize.c.back 2007-05-09 22:38:58.0 -0400
+++ gcc-4.1.0/gcc/tree-optimize.c 2007-05-09 22:38:31.0 -0400
@@ -389,9 +389,15 @@
break;
if (e)
{
- timevar_push (TV_INTEGRATION);
- optimize_inline_calls (fndecl);
- timevar_pop (TV_INTEGRATION);
+ for (e = node-callees; e; e = e-next_callee)
+ if (e-inline_failed !warn_inline)
+ break;
+ if (!e)
+ {
+ timevar_push (TV_INTEGRATION);
+ optimize_inline_calls (fndecl);
+ timevar_pop (TV_INTEGRATION);
+ }
}
}
/* We are not going to maintain the cgraph edges up to date.
/***
***/
Solution 2:
--- gcc-4.1.0/gcc/cgraphunit.c.back 2007-05-09 22:41:35.0 -0400
+++ gcc-4.1.0/gcc/cgraphunit.c 2007-05-09 22:24:21.0 -0400
@@ -1206,7 +1206,7 @@
if (dump_enabled_p (TDI_tree_all))
return true;
if (!cgraph_global_info_ready)
-return (DECL_INLINE (decl) !flag_really_no_inline);
+return ((DECL_INLINE (decl) !flag_really_no_inline)||lookup_attribute
(always_inline, DECL_ATTRIBUTES (decl)));
/* Look if there is any clone around. */
for (node = cgraph_node (decl); node; node = node-next_clone)
if (node-global.inlined_to)
--- gcc-4.1.0/gcc/tree-inline.c.back2007-05-09 22:41:18.0 -0400
+++ gcc-4.1.0/gcc/tree-inline.c 2007-05-09 22:35:12.0 -0400
@@ -1594,6 +1594,8 @@
}
/* Squirrel away the result so that we don't have to check again. */
+ if (lookup_attribute (always_inline, DECL_ATTRIBUTES (fn)))
+inlinable = true;
DECL_UNINLINABLE (fn) = !inlinable;
return inlinable;
/***
***/
Sincerely yours
Zhouyi Zhou
--
Summary: (different from bug report c/31077 and 29241) C handling
of always_inline attribute error and a solution
Product: gcc
Version: 4.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: zhouyi04 at ios dot cn
GCC build triplet: Linux i686 GNU/Linux
GCC host triplet: Linux i686 GNU/Linux
GCC target triplet: Linux i686 GNU/Linux
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31886
[Bug c/31886] (different from bug report c/31077 and 29241) C handling of always_inline attribute error and a solution
--- Comment #1 from pinskia at gcc dot gnu dot org 2007-05-10 04:19 --- I don't think this is a bug. The documentation for always inline says: For functions declared inline, this attribute inlines the function even if no optimization level was specified. That quote is from: http://gcc.gnu.org/onlinedocs/gcc-4.1.2/gcc/Function-Attributes.html And it is also in: http://gcc.gnu.org/onlinedocs/gcc-4.0.2/gcc/Function-Attributes.html alloc_null_binding is not declared inline so how do you think GCC will inline this function? -- pinskia at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |WAITING Summary|(different from bug report |(different from bug report |c/31077 and 29241) C|c/31077 and 29241) C |handling of always_inline |handling of always_inline |attribute error and a |attribute error and a |solution|solution http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31886
[Bug c/31886] (different from bug report c/31077 and 29241) C handling of always_inline attribute error and a solution
--- Comment #2 from zhouzhouyi at ercist dot iscas dot ac dot cn 2007-05-10 04:41 --- Subject: Re: (different from bug report c/31077 and 29241) C handling of always_inline attribute error and a solution Dear pinskia, If you lookup my solution current handling of conditions for optimize_inline_calls in tree_rest_of_compilation is obvious not good. Sincerely yours Zhouyi Zhou On 10 May 2007 03:19:10 - pinskia at gcc dot gnu dot org [EMAIL PROTECTED] wrote: --- Comment #1 from pinskia at gcc dot gnu dot org 2007-05-10 04:19 --- I don't think this is a bug. The documentation for always inline says: For functions declared inline, this attribute inlines the function even if no optimization level was specified. That quote is from: http://gcc.gnu.org/onlinedocs/gcc-4.1.2/gcc/Function-Attributes.html And it is also in: http://gcc.gnu.org/onlinedocs/gcc-4.0.2/gcc/Function-Attributes.html alloc_null_binding is not declared inline so how do you think GCC will inline this function? -- pinskia at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |WAITING Summary|(different from bug report |(different from bug report |c/31077 and 29241) C|c/31077 and 29241) C |handling of always_inline |handling of always_inline |attribute error and a |attribute error and a |solution|solution http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31886 --- You are receiving this mail because: --- You reported the bug, or are watching the reporter. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31886
[Bug c/31886] (different from bug report c/31077 and 29241) C handling of always_inline attribute error and a solution
--- Comment #3 from zhouzhouyi at ercist dot iscas dot ac dot cn 2007-05-10 04:43 --- Subject: Re: (different from bug report c/31077 and 29241) C handling of always_inline attribute error and a solution heh, pinkia, take a look at my solution1 On 10 May 2007 03:41:06 - zhouzhouyi at ercist dot iscas dot ac dot cn [EMAIL PROTECTED] wrote: --- Comment #2 from zhouzhouyi at ercist dot iscas dot ac dot cn 2007-05-10 04:41 --- Subject: Re: (different from bug report c/31077 and 29241) C handling of always_inline attribute error and a solution Dear pinskia, If you lookup my solution current handling of conditions for optimize_inline_calls in tree_rest_of_compilation is obvious not good. Sincerely yours Zhouyi Zhou On 10 May 2007 03:19:10 - pinskia at gcc dot gnu dot org [EMAIL PROTECTED] wrote: --- Comment #1 from pinskia at gcc dot gnu dot org 2007-05-10 04:19 --- I don't think this is a bug. The documentation for always inline says: For functions declared inline, this attribute inlines the function even if no optimization level was specified. That quote is from: http://gcc.gnu.org/onlinedocs/gcc-4.1.2/gcc/Function-Attributes.html And it is also in: http://gcc.gnu.org/onlinedocs/gcc-4.0.2/gcc/Function-Attributes.html alloc_null_binding is not declared inline so how do you think GCC will inline this function? -- pinskia at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |WAITING Summary|(different from bug report |(different from bug report |c/31077 and 29241) C|c/31077 and 29241) C |handling of always_inline |handling of always_inline |attribute error and a |attribute error and a |solution|solution http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31886 --- You are receiving this mail because: --- You reported the bug, or are watching the reporter. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31886 --- You are receiving this mail because: --- You reported the bug, or are watching the reporter. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31886
[Bug c/31886] (different from bug report c/31077 and 29241) C handling of always_inline attribute error and a solution
--- Comment #4 from zhouyi04 at ios dot cn 2007-05-10 05:33 --- Dear Pinsky In addition, The problem will still exists even add a inline to line 1 of the program, unless you add a static to line 1. Sincerely yours Zhouyi Zhou -- zhouyi04 at ios dot cn changed: What|Removed |Added CC||zhouyi04 at ios dot cn http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31886
gcc-bug-report- Tuesday May 08 - Portugal
According to http://gcc.gnu.org/bugs.html here is what is requested for a bug report. Regards, Miguel Luis. ## the exact version of GCC; $ gcc --version gcc (GCC) 4.1.2 (Ubuntu 4.1.2-0ubuntu4) Copyright (C) 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. $ ## the system type; $ uname -a Linux m0x 2.6.20-15-386 #2 Sun Apr 15 07:34:00 UTC 2007 i686 GNU/Linux $ ## the options given when GCC was configured/built; - Sorry but this is a binary package of gcc installed with build-essentials package in ubuntu and I don't know how to answer ## the complete command line that triggers the bug; $gcc -v -save-temps -c -g -ansi -Wall -O3 system.c ## the compiler output (error messages, warnings, etc.); $ make gcc -v -save-temps -c -g -ansi -Wall -O3 system.c Using built-in specs. Target: i486-linux-gnu Configured with: ../src/configure -v --enable-languages=c,c++,fortran,objc,obj-c++,treelang --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --program-suffix=-4.1 --enable-__cxa_atexit --enable-clocale=gnu --enable-libstdcxx-debug --enable-mpfr --enable-checking=release i486-linux-gnu Thread model: posix gcc version 4.1.2 (Ubuntu 4.1.2-0ubuntu4) /usr/lib/gcc/i486-linux-gnu/4.1.2/cc1 -E -quiet -v system.c -mtune=generic -ansi -Wall -fworking-directory -O3 -fpch-preprocess -o system.i ignoring nonexistent directory /usr/local/include/i486-linux-gnu ignoring nonexistent directory /usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../i486-linux-gnu/include ignoring nonexistent directory /usr/include/i486-linux-gnu #include ... search starts here: #include ... search starts here: /usr/local/include /usr/lib/gcc/i486-linux-gnu/4.1.2/include /usr/include End of search list. /usr/lib/gcc/i486-linux-gnu/4.1.2/cc1 -fpreprocessed system.i -quiet -dumpbase system.c -mtune=generic -ansi -auxbase system -g -O3 -Wall -ansi -version -fstack-protector -fstack-protector -o system.s GNU C version 4.1.2 (Ubuntu 4.1.2-0ubuntu4) (i486-linux-gnu) compiled by GNU C version 4.1.2 (Ubuntu 4.1.2-0ubuntu4). GGC heuristics: --param ggc-min-expand=99 --param ggc-min-heapsize=129470 Compiler executable checksum: c0d954aeefbb96d795ff3f6b3b72ef51 system.c: In function ‘system_verbose’: system.c:80: warning: implicit declaration of function ‘get_item_id_max_lenght’ system.c:80: internal compiler error: in fold_convert, at fold-const.c:1956 Please submit a full bug report, with preprocessed source if appropriate. See URL:http://gcc.gnu.org/bugs.html for instructions. For Debian GNU/Linux specific bug reporting instructions, see URL:file:///usr/share/doc/gcc-4.1/README.Bugs. Preprocessed source stored into /tmp/ccWfv49C.out file, please attach this to your bugreport. make: *** [system.o] Error 1 $ ## the /preprocessed/ file (|*.i*|) that triggers the bug, generated by adding |-save-temps| to the complete compilation command # 1 system.c # 1 /home/myk0n/symlink/xrtdb/current// # 1 built-in # 1 command line # 1 system.c # 1 /usr/include/stdio.h 1 3 4 # 28 /usr/include/stdio.h 3 4 # 1 /usr/include/features.h 1 3 4 # 323 /usr/include/features.h 3 4 # 1 /usr/include/sys/cdefs.h 1 3 4 # 313 /usr/include/sys/cdefs.h 3 4 # 1 /usr/include/bits/wordsize.h 1 3 4 # 314 /usr/include/sys/cdefs.h 2 3 4 # 324 /usr/include/features.h 2 3 4 # 346 /usr/include/features.h 3 4 # 1 /usr/include/gnu/stubs.h 1 3 4 # 1 /usr/include/bits/wordsize.h 1 3 4 # 5 /usr/include/gnu/stubs.h 2 3 4 # 1 /usr/include/gnu/stubs-32.h 1 3 4 # 8 /usr/include/gnu/stubs.h 2 3 4 # 347 /usr/include/features.h 2 3 4 # 29 /usr/include/stdio.h 2 3 4 # 1 /usr/lib/gcc/i486-linux-gnu/4.1.2/include/stddef.h 1 3 4 # 214 /usr/lib/gcc/i486-linux-gnu/4.1.2/include/stddef.h 3 4 typedef unsigned int size_t; # 35 /usr/include/stdio.h 2 3 4 # 1 /usr/include/bits/types.h 1 3 4 # 28 /usr/include/bits/types.h 3 4 # 1 /usr/include/bits/wordsize.h 1 3 4 # 29 /usr/include/bits/types.h 2 3 4 # 1 /usr/lib/gcc/i486-linux-gnu/4.1.2/include/stddef.h 1 3 4 # 32 /usr/include/bits/types.h 2 3 4 typedef unsigned char __u_char; typedef unsigned short int __u_short; typedef unsigned int __u_int; typedef unsigned long int __u_long; typedef signed char __int8_t; typedef unsigned char __uint8_t; typedef signed short int __int16_t; typedef unsigned short int __uint16_t; typedef signed int __int32_t; typedef unsigned int __uint32_t; __extension__ typedef signed long long int __int64_t; __extension__ typedef unsigned long long int __uint64_t; __extension__ typedef long long int __quad_t; __extension__ typedef unsigned long long int __u_quad_t; # 134 /usr/include/bits/types.h 3 4 # 1 /usr/include/bits/typesizes.h 1 3 4 # 135 /usr/include/bits/types.h 2 3 4 __extension__ typedef __u_quad_t __dev_t; __extension__ typedef unsigned int __uid_t; __extension__ typedef
bug report
I'm sending this mail to report a bug during the compilation of a Fortran program. The information needed are: Using built-in specs. Target: i686-apple-darwin8 Configured with: /private/var/tmp/gcc/gcc-5367.obj~1/src/configure --disable-checking -enable-werror --prefix=/usr --mandir=/share/man --enable-languages=c,objc,c++,obj-c++ --program-transform-name=/^[cg][^.-]*$/s/$/-4.0/ --with-gxx-include-dir=/include/c++/4.0.0 --with-slibdir=/usr/lib --build=powerpc-apple-darwin8 --with-arch=nocona --with-tune=generic --program-prefix= --host=i686-apple-darwin8 --target=i686-apple-darwin8 Thread model: posix gcc version 4.0.1 (Apple Computer, Inc. build 5367) After the followin command line: g77 NEWdistr_A_noCorrezione.f it shows this message: NEWdistr_A_noCorrezione.f: In program `doppioni': In file included from NEWdistr_A_noCorrezione.f:0: NEWdistr_A_noCorrezione.f:806: internal compiler error: in instantiate_virtual_regs_lossage, at function.c:3746 Please submit a full bug report, with preprocessed source if appropriate. See URL:http://gcc.gnu.org/bugs.html for instructions. This is it. I don't know if you need a copy of the program NEWdistr_A_noCorrezione.f. I attach it Thank you very much NEWdistr_A_noCorrezione.f Description: Binary data
Re: GCC bug report - Xubuntu kernel compile fails w/gcc bug report request
Jonathan Brickman wrote: as indicated by anyone who knows what I should be trying next! I tried to send this via the GCC web bug report system, but I could not find any way to attach this file, which the docs said is essential. First file the bug report, you will then immediately be taken to a page where you can attach the file to the newly created bug report. This is a bit awkward, yes, but I believe all bugzilla installations work this way. -- Jim Wilson, GNU Tools Support, http://www.specifix.com
BUG report : Internal compiler error
hi this is the error iam getting when i try to cross compile ltib BSP of linux 2.6.10 for arm11 platfrom from SUSE10 host arm-none-linux-gnueabi-ranlib ./libgcov.a arm-none-linux-gnueabi-gcc -O2 -DIN_GCC-W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -isystem ./include -fomit-frame-pointer -fPIC -g0 -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -I. -I. -I../../gcc -I../../gcc/. -I../../gcc/../include -fexceptions -c ../../gcc/unwind-dw2.c -o libgcc/./unwind-dw2.o ../../gcc/unwind-dw2.c: In function 'extract_cie_info': ../../gcc/unwind-dw2.c:328: warning: pointer targets in passing argument 1 of 'strlen' differ in signedness ../../gcc/unwind-dw2.c:381: warning: dereferencing type-punned pointer will break strict-aliasing rules ../../gcc/unwind-dw2.c: In function 'execute_cfa_program': ../../gcc/unwind-dw2.c:844: warning: dereferencing type-punned pointer will break strict-aliasing rules ../../gcc/unwind-dw2.c: In function 'uw_frame_state_for': ../../gcc/unwind-dw2.c:1060: warning: dereferencing type-punned pointer will break strict-aliasing rules ../../gcc/unwind-dw2.c: In function 'init_dwarf_reg_size_table': ../../gcc/unwind-dw2.c:1272: internal compiler error: in arm_dbx_register_number, at config/arm/arm.c:15183 Please suggest me to overcome this, Best regards sivakumar.R.J
bug report
1. configure options:
alfalfa:/home/zz/share/gcc.4.1/gcc-4.1.1:{1193} ./configure --prefix=
$HOME/local
2. make stage1 gcc-4.1.1
alfalfa:/home/zz/share/gcc.4.1/gcc-4.1.1:{1193} make boostrap
...
...
(stop at)
/home/zz/share/gcc.4.1/gcc-4.1.1/host-i386-redhat-linux/gcc/xgcc -
shared-libgcc -B/home/zz/share/gcc.4.1/gcc-4.1.1/host-i386-redhat-linux
/gcc -nostdinc++ -L/home/zz/share/gcc.4.1/gcc-4.1.1/i386-redhat-
linux/libstdc++-v3/src -L/home/zz/share/gcc.4.1/gcc-4.1.1/i386-redhat-
lin
ux/libstdc++-v3/src/.libs -B/usr/i386-redhat-linux/bin/ -B/usr/i386-
redhat-linux/lib/ -isystem /usr/i386-redhat-linux/include -isystem /u
sr/i386-redhat-linux/sys-include -shared -nostdlib /usr/lib/gcc/i386-
redhat-linux/../../crti.o /home/zz/share/gcc.4.1/gcc-4.1.1/host-i386
-redhat-
linux/gcc/crtbeginS.o .libs/bitmap_allocator.o .libs/pool_allocator.o
.libs/mt_allocator.o .libs/codecvt.o .libs/compatibility.o
.libs/complex_io.o .libs/ctype.o .libs/debug.o .libs/debug_list.o
.libs/functexcept.o .libs/globals_locale.o .libs/globals_io.o .libs/io
s.o .libs/ios_failure.o .libs/ios_init.o .libs/ios_locale.o .libs/limits.o
.libs/list.o .libs/locale.o .libs/locale_init.o .libs/locale_f
acets.o .libs/localename.o .libs/stdexcept.o .libs/strstream.o .libs/tree.o
.libs/allocator-inst.o .libs/concept-inst.o .libs/fstream-ins
t.o .libs/ext-inst.o .libs/ios-inst.o .libs/iostream-
inst.o .libs/istream-inst.o .libs/istream.o .libs/locale-
inst.o .libs/locale-misc-in
st.o .libs/misc-inst.o .libs/ostream-inst.o .libs/sstream-
inst.o .libs/streambuf-inst.o .libs/streambuf.o .libs/string-
inst.o .libs/valar
ray-inst.o .libs/wlocale-inst.o .libs/wstring-
inst.o .libs/atomicity.o.libs/codecvt_members.o .libs/collate_members.o
.libs/ctype_members
.o .libs/messages_members.o .libs/monetary_members.o .libs/numeric_members.o
.libs/time_members.o .libs/basic_file.o .libs/c++locale.o -W
l,--whole-archive ../libmath/.libs/libmath.a ../libsupc++/.libs/libsupc+
+convenience.a -Wl,--no-whole-archive -L/home/zz/share/gcc.4.1/g
cc-4.1.1/i386-redhat-linux/libstdc++-v3/src -
L/home/zz/share/gcc.4.1/gcc-4.1.1/i386-redhat-linux/libstdc++-
v3/src/.libs -lm ../libmath/.l
ibs/libmath.a -lm ../libsupc++/.libs/libsupc++convenience.a -lm -
L/home/zz/share/gcc.4.1/gcc-4.1.1/host-i386-redhat-linux/gcc -L/usr/lib/
gcc/i386-redhat-linux/../.. -lgcc_s -lc -lgcc_s -lm -lgcc_s -lc -
lgcc_s /home/zz/share/gcc.4.1/gcc-4.1.1/host-i386-redhat-linux/gcc/crt
endS.o /usr/lib/gcc/i386-redhat-linux/../../crtn.o -Wl,-O1 -Wl,-z -
Wl,relro -Wl,--version-script=libstdc++-symbol.ver -Wl,-soname -Wl,li
bstdc++.so.6 -o .libs/libstdc++.so.6.0.8
/usr/bin/ld: BFD 2.15.92.0.2 20040927 internal error, aborting
at ../../bfd/elf32-i386.c line 2262 in elf_i386_relocate_section
/usr/bin/ld: Please report this bug.
collect2: ld returned 1 exit status
make[4]: *** [libstdc++.la] Error 1
make[4]: Leaving directory `/home/zz/share/gcc.4.1/gcc-4.1.1/i386-
redhat-linux/libstdc++-v3/src'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/home/zz/share/gcc.4.1/gcc-4.1.1/i386-
redhat-linux/libstdc++-v3'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/home/zz/share/gcc.4.1/gcc-4.1.1/i386-
redhat-linux/libstdc++-v3'
make[1]: *** [all-target-libstdc++-v3] Error 2
make[1]: Leaving directory `/home/zz/share/gcc.4.1/gcc-4.1.1'
make: *** [all] Error 2
3. used gcc version:
alfalfa:/home/zz/share/gcc.4.1/gcc-4.1.1:{1192}gcc -v
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
--infodir=/usr/share/info --enable-shared --enable-threads=posix
--disable-checking --with-system-zlib --enable-__cxa_atexit
--disable-libunwind-exceptions --enable-java-awt=gtk --host=i386-redhat-
linux
Thread model: posix
gcc version 3.4.5 20051201 (Red Hat 3.4.5-2)
4. system hardware info
SONY CD-RW/DVD CRX310EE
USB,SOUND,IDE intel 82801EB
VIDEO nvidia
NET DEV intel 82845GM
HD seagate 3802110A
FIREWIRE TI
SYSTEM DV intel bridges
bug report
a bug in mingw
//this shows that the older version of mingw32 can be better than the newer one
#include iostream.h
#include fstream.h
#include conio.h
main()
{
//the string should be written two times if the file exists
ifstream xyz;
char chr;
xyz.open(a.bat);
while(xyz.get(chr)) coutchr; //INFO: it always works
xyz.close();
xyz.open(a.bat); //on the newer version, the file is not opened
while(xyz.get(chr)) coutchr; //INFO: it works on the older version ONLY
getch();
//newer version 3.4.2 (Dev-Cpp 4.9.9.2)
//older: 2.95.3-6 (Dev-Cpp 4.9.6.0)
//parameters:
//older version: d:\progra~1\dev-cpp\bin\g++.exe bug.cpp -o bug.exe -s
//newer version: d:\windows\dev-cpp\bin\g++.exe bug.cpp -o bug.exe -s
//Sławomir N., Poland
}
/*[EMAIL PROTECTED]*/
// probably the xyz.close() function does not work corectly
Re: bug report
Hayashi Eisuke wrote: 100: 400 (-1077752048) 2092728: Segmentatioin error (core dumped) The process is dying because you are exceeding unix process stack space limits. You probably have an 8MB per process limit, and the number you are using is a tad less than 2MB. If you are using bash, see the documentation for the ulimit command. If csh, I think it is limits. -- Jim Wilson, GNU Tools Support, http://www.specifix.com
Re: bug report
DEAR Sir : GNU
I am writing to you regarding bug report
It resulted based on the last point when having experimented ..the
following...
#include stdio.h
#include values.h
void subroutine(int n)
{
int buf[n];
fprintf(stderr, %d (%d)\n, (int)sizeof(buf), (unsigned long)buf);
}
int main( int argc, char **argv)
{
int i, value[] = {200, 250, 300};
for (i=0; i3; i++) {
fprintf(stderr, %d: , value[i]);
subroutine(value[i]);
}
exit(0);
}
① gcc version 2.96 2731 (Red Hat Linux 7.3 2.96-110)
stacksize 8192 kbytes
200: 800 (-1081748336)
250: segmentation fault (core dumped)
② gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-52)
stacksize 10240 kbytes
200: 800 (-1081748128)
250: 1000 (-1083748128)
300: segmentation fault (core dumped)
It was not bug of gcc but it was a problem of stacksize.
Thanks.
Sincerely yours,
EISUKE HAYASHI
Jim Wilson wrote:
Hayashi Eisuke wrote:
100: 400 (-1077752048)
2092728: Segmentatioin error (core dumped)
The process is dying because you are exceeding unix process stack space
limits. You probably have an 8MB per process limit, and the number you
are using is a tad less than 2MB.
If you are using bash, see the documentation for the ulimit command.
If csh, I think it is limits.
--
Jim Wilson, GNU Tools Support, http://www.specifix.com
bug report
DEAR Sir : GNU
I am writing to you regarding bug report
about under this code
aaa(int bbb) {
char *ccc[bbb]
}
gcc response no error. but memory error occured.
Sincerely yours,
EISUKE HAYASHI
Re: bug report
Hi Hayashi-san,
I am writing to you regarding bug report
about under this code
aaa(int bbb) {
char *ccc[bbb]
}
gcc response no error. but memory error occured.
GCC accepts this as an extension to the ISO C 90 and ISO C++
languages by default. The extension is called Variable Length
Arrays and it is officially part of the ISO C99 language.
Thanks,
Andrew Pinski
bug report
DEAR Sir : GNU
I am writing to you regarding bug report
under this code
#include stdio.h
#include values.h
void subroutine(int n)
{
int buf[n];
fprintf(stderr, %d (%d)\n, (int)sizeof(buf), (unsigned long)buf);
}
int main( int argc, char **argv)
{
int i, value[] = {0, 1, -1, INT_MAX, 100, 2092728, 2092729};
for (i=0; i7; i++) {
fprintf(stderr, %d: , value[i]);
subroutine(value[i]);
}
exit(0);
}
① gcc version 3.2.3
0: 0 (-1073762400)
1: 4 (-1073762416)
-1: -4 (-1073762400)
2147483647: -4 (-1073762400)
100: 400 (-1077762400)
2092728: 8370912 (-1082133312)
2092729: 8370916 (-1082133328)
② gcc version 2.96
0: 0 (-1073752048)
1: 4 (-1073752064)
-1: -4 (-1073752048)
2147483647: -4 (-1073752048)
100: 400 (-1077752048)
2092728: Segmentatioin error (core dumped)
There was a difference of the above-mentioned by the difference of the
version of gcc when having thoroughly examined it. Was this a bug of
version 2.96?
Sincerely yours,
EISUKE HAYASHI
Bug report - unrecognizable insn
Hi All, Bug encountered building X. Probably already reported but I couldn't find any reference. I did google... Commandline.. make World CROSSCOMPILEDIR=/usr/local/arm-linux/bin X version XFree86-4.5.0, first 3 source archives only. Following instructions for configuring as per http://www.handhelds.org/minihowto/building-x.html at least the host.def and make command, tweaked for my cross tools installation. [EMAIL PROTECTED]:~$ arm-xscale-linux-gnu-gcc -v Reading specs from /usr/local/arm-linux/gcc-3.4.4-glibc-2.3.5/arm-xscale-linux-gnu/lib/gcc/arm-xscale-linux-gnu/3.4.4/specs Configured with: /usr/src/arm-linux/crosstool-0.38/build/arm-xscale-linux-gnu/gcc-3.4.4-glibc-2.3.5/gcc-3.4.4/configure --target=arm-xscale-linux-gnu --host=i686-host_pc-linux-gnu --prefix=/usr/local/arm-linux/gcc-3.4.4-glibc-2.3.5/arm-xscale-linux-gnu --with-cpu=xscale --enable-cxx-flags=-mcpu=xscale --with-headers=/usr/local/arm-linux/gcc-3.4.4-glibc-2.3.5/arm-xscale-linux-gnu/arm-xscale-linux-gnu/include --with-local-prefix=/usr/local/arm-linux/gcc-3.4.4-glibc-2.3.5/arm-xscale-linux-gnu/arm-xscale-linux-gnu --disable-nls --enable-threads=posix --enable-symvers=gnu --enable-__cxa_atexit --enable-languages=c,c++ --enable-shared --enable-c99 --enable-long-long Thread model: posix gcc version 3.4.4 [EMAIL PROTECTED]:~$ make[3]: Entering directory `/usr/src/arm-linux/apps/XFree86/build/programs/Xserver/GL/mesa/swrast' rm -f s_depth.o /usr/local/arm-linux/bin/`echo /usr/local/arm-linux/bin/arm-xscale-linux-gnu-gcc|sed s%.*/%%` -c -O2 -fsigned-char -I../../../../../extras/Mesa/src/mesa -I../../../../../extras/Mesa/src/mesa/main -I../../../../../extras/Mesa/src/mesa/glapi -I../../../../../extras/Mesa/src/mesa/shader -I../../../../../extras/Mesa/src/mesa/swrast -I../../../../../extras/Mesa/src/mesa/swrast_setup -I../../../../../extras/Mesa/include -I../../../../../programs/Xserver/include -I../../../../../exports/include/X11 -I../../../../../programs/Xserver/GL/include -I../../../../../programs/Xserver/GL/glx -I../../../../../lib/GL/include -I../../../../../programs/Xserver/hw/xfree86 -I../../../../../exports/include -I../../../../.. -I../../../../../exports/include -Dlinux -D__arm__ -D_POSIX_SOURCE -D_BSD_SOURCE -D_GNU_SOURCE -DX_LOCALE -DSHAPE -DXINPUT -DXKB -DLBX -DXAPPGROUP -DXCSECURITY -DTOGCUP -DXF86BIGFONT -DDPMSExtension -DPIXPRIV -DPANORAMIX -DRENDER -DRANDR -DGCCUSESGAS -DAVOID_GLYPHBLT -DPIXPRIV -DSINGLEDEPTH -DXFreeXDGA -DXvExtension-DXFree86LOADER -DXFree86Server-DXF86VIDMODE -DXvMCExtension -DSMART_SCHEDULE -DBUILDDEBUG -DXResExtension -DX_BYTE_ORDER=X_LITTLE_ENDIAN -DNDEBUG -DNEED_STRLCAT -DFUNCPROTO=15 -DNARROWPROTO -DGLXEXT -DGLX_USE_MESA s_depth.c s_depth.c: In function `_swrast_depth_test_span': s_depth.c:1362: error: unrecognizable insn: (insn 5699 1829 1835 209 s_depth.c:820 (set (reg:HI 2 r2) (mem:HI (plus:SI (mult:SI (reg/v:SI 5 r5 [orig:557 i ] [557]) (const_int 4 [0x4])) (reg/v/f:SI 8 r8 [orig:85 z ] [85])) [3 S4 A32])) -1 (nil) (nil)) s_depth.c:1362: internal compiler error: in extract_insn, at recog.c:2083 Please submit a full bug report, with preprocessed source if appropriate. See URL:http://gcc.gnu.org/bugs.html for instructions. make[3]: *** [s_depth.o] Error 1 make[3]: Leaving directory `/usr/src/arm-linux/apps/XFree86/build/programs/Xserver/GL/mesa/swrast' Need any more info? Have fun! Regards, James.
gcc 4.0.2 bug report
Hi, gcc team!
i unfortunately cannot use the bug db for this report because i am not
allowed to use this email address for websites, mailing lists, etc.
Bug summary: The two-arg form of std::random_shuffle() shuffles predictably
unless srand() is called beforehand.
GCC version:
gcc (GCC) 4.0.2
Copyright (C) 2005 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
// -
// Begin source code:
#include string // std::string
#include vector // std::string
#include iostream // cout/cerr
#include iterator
#include algorithm // cout/cerr
#include stdlib.h // rand(), srand()
#include time.h // time()
int main( int argc, char **argv )
{
//srand(time(NULL));
// ACHTUNG: if srand() is not called then random_shuffle() always
// shuffles with the same results. This is undocumented behaviour
// and is probably limited to the GNU/GCC STL implementation.
// No STL documentation i have ever read (or can find at the moment)
// calls for explicitely seeding the RNG used by random_shuffle().
typedef std::vectorstd::string SVec;
SVec vec;
std::string line;
while( std::getline( std::cin, line ) ) {
vec.push_back( line );
}
std::random_shuffle( vec.begin(), vec.end() );
std::copy( vec.begin(), vec.end(),
std::ostream_iteratorstd::string( std::cout, \n ) );
return 0;
}
//--
//end source code
Compile with:
gcc -o shuffle shuffle.cpp -lstdc++
Reproducing the behaviour:
Run on any list of input (e.g., a file with the numbers 1..5, one
number
per line), and repeat this any number of times. The results of the shuffling
will always be the same. e.g.: Input file 'foo' contains the letters d c b
a,
one per line and in that order:
for i in 1 1 1 1 1; do ./shuffle foo; sleep 1; done
d
a
c
b
d
a
c
b
d
a
c
b
d
a
c
b
d
a
c
b
Workaround: If the srand() line is uncommented, random_shuffle() shuffles
unpredictably (as
it should).
i have not found any STL documentation stating that the underlying system
RNG must be seeded
before using random_shuffle(), and can also find no examples on the web
demonstrating that it
should/must be seeded for proper operation. IMO this places an unwarranted
(and certainly
undocumented) expectation on the user.
Take care,
- stephan beal
GCC bug report: incorrect assertion in PCH
I'm describing a error which occures when running GCC 4.0.2 compiled with internal coverage checks (when gcc_assert() produces code). There is a place in 'ggc-common.c' at line 870: gcc_assert (!*slot); This assertion ALWAYS fail when using the PCH. I think it must be removed. Edward Chernenko, [EMAIL PROTECTED] __ Yahoo! DSL Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com
Compiler bug report
Hello, For my project, i am using Altera Excalibur EPXA1 board. i got Linux2.4.21 with patch-2.4.21-rmk2, which support EXPA1 board for ARM. I am using Altera provided Quartus II 4.0 tools. this tools also provide the arm-gnupro tool. which has arm-elf- cross-compiler. i config the kernel, build the dependencies and at time of building the kernel image it give the 'compiler cpp fatal signal 13 error' make epxa1db_config make oldconfig make dep make zImage ormake vmlinux now i am stuck here. please! anyone suggest me the bug fix for this problem... now i am pasting the error report which i got while building the kernel image. make[2]: Entering directory `/home/goutam/Dump-2.4.21/linux-2.4.21/fs' /home/mitul/arm_cross/bin/arm-elf-gcc -D__KERNEL__ -I/home/goutam/Dump-2.4.2 1/linux-2.4.21/include -Wall -Wstrict-prototypes -Wno-trigraphs -Os -fno-strict-aliasing -fno-common -Uarm -fno-common -pipe -g -mapcs-32 -D__LINUX_ARM_ARCH__=4 -march=armv4 -mtune=arm9tdmi -mshort-load-bytes -msoft-float -Uarm -nostdinc -iwithprefix include -DKBUILD_BASENAME=locks -c -o locks.o locks.c In file included from /home/goutam/Dump-2.4.21/linux-2.4.21/include/linux/string.h:25, from /home/goutam/Dump-2.4.21/linux-2.4.21/include/linux/fs.h:23, from /home/goutam/Dump-2.4.21/linux-2.4.21/include/linux/capability.h:17, from /home/goutam/Dump-2.4.21/linux-2.4.21/include/linux/binfmts.h:5, from /home/goutam/Dump-2.4.21/linux-2.4.21/include/linux/sched.h:9, from /home/goutam/Dump-2.4.21/linux-2.4.21/include/linux/mm.h:4, from /home/goutam/Dump-2.4.21/linux-2.4.21/include/linux/slab.h:14, from locks.c:118: /home/goutam/Dump-2.4.21/linux-2.4.21/include/asm/string.h:16: warning: conflicting types for built-in function `memcpy' /home/goutam/Dump-2.4.21/linux-2.4.21/include/asm/string.h:26: warning: conflicting types for built-in function `memset' In file included from /home/goutam/Dump-2.4.21/linux-2.4.21/include/linux/fs.h:23, from /home/goutam/Dump-2.4.21/linux-2.4.21/include/linux/capability.h:17, from /home/goutam/Dump-2.4.21/linux-2.4.21/include/linux/binfmts.h:5, from /home/goutam/Dump-2.4.21/linux-2.4.21/include/linux/sched.h:9, from /home/goutam/Dump-2.4.21/linux-2.4.21/include/linux/mm.h:4, from /home/goutam/Dump-2.4.21/linux-2.4.21/include/linux/slab.h:14, from locks.c:118: /home/goutam/Dump-2.4.21/linux-2.4.21/include/linux/string.h:77: warning: conflicting types for built-in function `memcmp' In file included from /home/goutam/Dump-2.4.21/linux-2.4.21/include/linux/fs.h:703, from /home/goutam/Dump-2.4.21/linux-2.4.21/include/linux/capability.h:17, from /home/goutam/Dump-2.4.21/linux-2.4.21/include/linux/binfmts.h:5, from /home/goutam/Dump-2.4.21/linux-2.4.21/include/linux/sched.h:9, from /home/goutam/Dump-2.4.21/linux-2.4.21/include/linux/mm.h:4, from /home/goutam/Dump-2.4.21/linux-2.4.21/include/linux/slab.h:14, from locks.c:118: /home/goutam/Dump-2.4.21/linux-2.4.21/include/linux/udf_fs_sb.h:21: warning: ignoring pragma: /home/goutam/Dump-2.4.21/linux-2.4.21/include/linux/udf_fs_sb.h:76: warning: ignoring pragma: locks.c: In function `flock_make_lock': locks.c:239: Internal compiler error in `output_move_double', at config/arm/arm.c:5125 Please submit a full bug report. See URL:http://www.gnu.org/software/gcc/faq.html#bugreport for instructions. arm-elf-gcc: Internal compiler error: program cpp got fatal signal 13 make[2]: *** [locks.o] Error 1 make[2]: Leaving directory `/home/goutam/Dump-2.4.21/linux-2.4.21/fs' make[1]: *** [first_rule] Error 2 make[1]: Leaving directory `/home/goutam/Dump-2.4.21/linux-2.4.21/fs' make: *** [_dir_fs] Error 2 [EMAIL PROTECTED] linux-2.4.21]# i am attached the error report. kindly view, if make[2]: Entering directory `/home/goutam/Dump-2.4.21/linux-2.4.21/fs' /home/mitul/arm_cross/bin/arm-elf-gcc -D__KERNEL__ -I/home/goutam/Dump-2.4.21/linux-2.4.21/include -Wall -Wstrict-prototypes -Wno-trigraphs -Os -fno-strict-aliasing -fno-common -Uarm -fno-common -pipe -g -mapcs-32 -D__LINUX_ARM_ARCH__=4 -march=armv4 -mtune=arm9tdmi -mshort-load-bytes -msoft-float -Uarm -nostdinc -iwithprefix include -DKBUILD_BASENAME=locks -c -o locks.o locks.c In file included from /home/goutam/Dump-2.4.21/linux-2.4.21/include/linux/string.h:25, from /home/goutam/Dump-2.4.21/linux-2.4.21/include/linux/fs.h:23, from /home/goutam/Dump-2.4.21/linux-2.4.21
Compiler bug report
Hello, For my project, i am using Altera Excalibur EPXA1 board. i got Linux2.4.21 with patch-2.4.21-rmk2, which support EXPA1 board for ARM. I am using Altera provided Quartus II 4.0 tools. this tools also provide the arm-gnupro tool. which has arm-elf- cross- compiler. i config the kernel, build the dependencies and at time of building the kernel image it give the 'compiler cpp fatal signal 13 error' make epxa1db_config make oldconfig make dep make zImage ormake vmlinux now i am stuck here. please! anyone suggest me the bug fix for this problem... now i am pasting the error report which i got while building the kernel image. make[2]: Entering directory `/home/goutam/Dump-2.4.21/linux- 2.4.21/fs' /home/mitul/arm_cross/bin/arm-elf-gcc -D__KERNEL__ - I/home/goutam/Dump-2.4.21/linux-2.4.21/include -Wall -Wstrict- prototypes -Wno-trigraphs -Os -fno-strict-aliasing -fno-common -Uarm - fno-common -pipe -g -mapcs-32 -D__LINUX_ARM_ARCH__=4 - march=armv4 -mtune=arm9tdmi -mshort-load-bytes -msoft-float -Uarm - nostdinc -iwithprefix include -DKBUILD_BASENAME=locks -c -o locks.o locks.c In file included from /home/goutam/Dump-2.4.21/linux- 2.4.21/include/linux/string.h:25, from /home/goutam/Dump-2.4.21/linux- 2.4.21/include/linux/fs.h:23, from /home/goutam/Dump-2.4.21/linux- 2.4.21/include/linux/capability.h:17, from /home/goutam/Dump-2.4.21/linux- 2.4.21/include/linux/binfmts.h:5, from /home/goutam/Dump-2.4.21/linux- 2.4.21/include/linux/sched.h:9, from /home/goutam/Dump-2.4.21/linux- 2.4.21/include/linux/mm.h:4, from /home/goutam/Dump-2.4.21/linux- 2.4.21/include/linux/slab.h:14, from locks.c:118: /home/goutam/Dump-2.4.21/linux- 2.4.21/include/asm/string.h:16: warning: conflicting types for built-in function `memcpy' /home/goutam/Dump-2.4.21/linux- 2.4.21/include/asm/string.h:26: warning: conflicting types for built-in function `memset' In file included from /home/goutam/Dump-2.4.21/linux- 2.4.21/include/linux/fs.h:23, from /home/goutam/Dump-2.4.21/linux- 2.4.21/include/linux/capability.h:17, from /home/goutam/Dump-2.4.21/linux- 2.4.21/include/linux/binfmts.h:5, from /home/goutam/Dump-2.4.21/linux- 2.4.21/include/linux/sched.h:9, from /home/goutam/Dump-2.4.21/linux- 2.4.21/include/linux/mm.h:4, from /home/goutam/Dump-2.4.21/linux- 2.4.21/include/linux/slab.h:14, from locks.c:118: /home/goutam/Dump-2.4.21/linux- 2.4.21/include/linux/string.h:77: warning: conflicting types for built-in function `memcmp' In file included from /home/goutam/Dump-2.4.21/linux- 2.4.21/include/linux/fs.h:703, from /home/goutam/Dump-2.4.21/linux- 2.4.21/include/linux/capability.h:17, from /home/goutam/Dump-2.4.21/linux- 2.4.21/include/linux/binfmts.h:5, from /home/goutam/Dump-2.4.21/linux- 2.4.21/include/linux/sched.h:9, from /home/goutam/Dump-2.4.21/linux- 2.4.21/include/linux/mm.h:4, from /home/goutam/Dump-2.4.21/linux- 2.4.21/include/linux/slab.h:14, from locks.c:118: /home/goutam/Dump-2.4.21/linux- 2.4.21/include/linux/udf_fs_sb.h:21: warning: ignoring pragma: /home/goutam/Dump-2.4.21/linux- 2.4.21/include/linux/udf_fs_sb.h:76: warning: ignoring pragma: locks.c: In function `flock_make_lock': locks.c:239: Internal compiler error in `output_move_double', at config/arm/arm.c:5125 Please submit a full bug report. See URL:http://www.gnu.org/software/gcc/faq.html#bugreport for instructions. arm-elf-gcc: Internal compiler error: program cpp got fatal signal 13 make[2]: *** [locks.o] Error 1 make[2]: Leaving directory `/home/goutam/Dump-2.4.21/linux- 2.4.21/fs' make[1]: *** [first_rule] Error 2 make[1]: Leaving directory `/home/goutam/Dump-2.4.21/linux- 2.4.21/fs' make: *** [_dir_fs] Error 2 [EMAIL PROTECTED] linux-2.4.21]# i am attached the error report. kindly view, if The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s)and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender or [EMAIL PROTECTED]
Re: Compiler bug report
[EMAIL PROTECTED] wrote: I am using Altera provided Quartus II 4.0 tools. this tools also provide the arm-gnupro tool. which has arm-elf- cross- compiler. We can't fix problems in compiler releases made by other people. gnupro is a Red Hat trademark. We only support FSF gcc releases here. You can try contacting the people you got the compiler release from, or you can try an FSF gcc release. please! anyone suggest me the bug fix for this problem... now i am pasting the error report which i got while building the kernel image. This bug report is lacking info we normally need. Gcc version info. A testcase that can reproduce the bug. Etc. See http://gcc.gnu.org/bugs.html for info on how to report bugs. Also, bugs should be reported into our bugzilla bug database instead of emailed to this list. -- Jim Wilson, GNU Tools Support, http://www.specifix.com
Re: gfortran says to submit bug report
On Sep 28, 2005, at 4:53 PM, Joe Koski wrote: While attempting to compile the NIST FDS4 code (f90 based) I get the following error and a request to submit a bug report: jakoski$ gfortran -c -O3 -ffixed-form -fno-underscoring mods.f mods.f: In function 'lpcoef': mods.f:5099: error: unrecognizable insn: (insn 613 612 614 22 (set (reg:DF 729) (subreg:DF (mem/s:DC (plus:SI (reg/f:SI 114 virtual-stack-vars) (const_int 56112 [0xdb30])) [1413 equiv.1.cm+32 S16 A64]) 8)) -1 (nil) (nil)) mods.f:5099: internal compiler error: in extract_insn, at recog.c:2082 Please submit a full bug report, with preprocessed source if appropriate. See URL:http://gcc.gnu.org/bugs.html for instructions. The compiler that I am using (and can get) is: Joe-Koskis-Computer:~/Fortran_Compiles/fds_test_compile_gfortran/ compiler error jakoski$ gfortran -v Using built-in specs. Target: powerpc-apple-darwin7.9.0 Configured with: ../gcc/configure --enable-languages=c++,f95 Thread model: posix gcc version 4.1.0 20050517 (experimental) Can you try a new compiler as the one which you are using is more than 4 months old and I think this has already been fixed. Thanks, Andrew Pinski
[Bug c/21446] New: internal compiler error -- is recommending to file a bug report
Trying to build gcc-3.4.3 for IBM AIX 5.3L on an IBM p570 machine. Fails, and a message asks me to file a bug report. I have generated the .i file using ./xgcc -v -save-temps ... ... but I don't see a way to attach the .i file (and .s file if you need) in this Bugzilla form. I can email it on request. sdp1:/oracle/node1/gccbuild/gcc./xgcc -v Using built-in specs. Configured with: /oracle/node1/gcc-3.4.3/configure -- prefix=/oracle/node1/gccinstall --enable-threads --enable-languages=c,c++ Thread model: aix gcc version 3.4.3 /xgcc -B./ -B/oracle/node1/gccinstall/powerpc-ibm-aix5.3.0.0/bin/ - isystem /oracle/node1/gccinstall/powerpc-ibm-aix5.3.0.0/include - isystem /oracle/node1/gccinstall/powerpc-ibm-aix5.3.0.0/sys-include - L/oracle/node1/gccbuild/gcc/../ld -O2 -DIN_GCC-W -Wall -Wwrite-strings - Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition - isystem ./include -g -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 - D__GCC_FLOAT_NOT_NEEDED -I. -I. -I/oracle/node1/gcc-3.4.3/gcc - I/oracle/node1/gcc-3.4.3/gcc/. -I/oracle/node1/gcc-3.4.3/gcc/../include - I../intl -DL_fixunsdfsi -c /oracle/node1/gcc-3.4.3/gcc/libgcc2.c -o libgcc/./_fixunsdfsi.o /oracle/node1/gcc-3.4.3/gcc/libgcc2.c: In function `__fixunsdfsi': /oracle/node1/gcc-3.4.3/gcc/libgcc2.c:1384: error: unrecognizable insn: (insn:HI 11 10 12 0 /oracle/node1/gcc-3.4.3/gcc/libgcc2.c:1381 (set (reg:CCEQ 122) (compare:CCEQ (ior:SI (gt:SI (reg:CCFP 121) (const_int 0 [0x0])) (eq:SI (reg:CCFP 121) (const_int 0 [0x0]))) (const_int 1 [0x1]))) -1 (insn_list 10 (nil)) (expr_list:REG_DEAD (reg:CCFP 121) (nil))) /oracle/node1/gcc-3.4.3/gcc/libgcc2.c:1384: internal compiler error: in extract_insn, at recog.c:2083 Please submit a full bug report, with preprocessed source if appropriate. See URL:http://gcc.gnu.org/bugs.html for instructions. make[3]: *** [libgcc/./_fixunsdfsi.o] Error 1 make[3]: Leaving directory `/oracle/node1/gccbuild/gcc' make[2]: *** [stmp-multilib] Error 2 make[2]: Leaving directory `/oracle/node1/gccbuild/gcc' make[1]: *** [stage1_build] Error 2 make[1]: Leaving directory `/oracle/node1/gccbuild/gcc' make: *** [bootstrap] Error 2 sdp1:/oracle/node1/gccbuild -- Summary: internal compiler error -- is recommending to file a bug report Product: gcc Version: 3.4.3 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: philip dot thambidurai at comverse dot com CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21446
[Bug c/21446] internal compiler error -- is recommending to file a bug report
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-05-07 19:33 --- *** This bug has been marked as a duplicate of 9382 *** -- What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||DUPLICATE http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21446
Re: bug report for gfortran
On Apr 28, 2005, at 2:41 PM, Dutta, Kalyan wrote: I am submitting a bug report for GNU's Fortran95 compiler, gfortran. I realize the compiler is experimental. Any help you might be able to provide will be appreciated. I am Emailing this report because I couldn't successfully attach the requested preprocessor file via GNU's Bugzilla site ... This is most likely PR 21034. You have to attach the .f files after submitting the bug. -- Pinski
GCC bug report
hi there,
I'd like to report a bug with the 'gcc' and its optimizer:
the attached file 'compilerbug.txt' contains the compiler version,
the command line and the compiler output.
find also attached the source '2m_tpl.c' and the preprocessed file
'2m_tpl.i'
Without the optimizer, the file compiles ok.
We have another file in the project that triggers the same intenal error,
while all the (hundred) others are ok.
What these two files have in common is the rather large number of
local variables.
If there's no immediate fix for the compiler, probably you could tell
me a workaround by turning on or off particular compiler option(s) ?
kind regards
Gerhard DonGerry Jacobs
MarconiONDATABacknang Tel. 07191/13- 3083
[EMAIL PROTECTED]Fax 07191/13-63083
One man's error is another man's data
# COMPILER VERSION
Reading specs from
/home_bk6914/shw2bk/usr/local/bin/../lib/gcc-lib/m68k-elf/3.3.3/specs
Configured with: /usr/local/src/uclinux-tools/gcc-3.3-20031222/configure
--enable-languages=c,c++ --target=m68k-elf --enable-multilib
--enable-target-optspace --with-gnu-ld --disable-nls --disable-__cxa_atexit
--disable-c99 --disable-clocale --disable-c-mbchar --disable-long-long
--enable-cxx-flags=-D_ISOC99_SOURCE -D_BSD_SOURCE
Thread model: single
gcc version 3.3.3 20031222 (prerelease)
# COMPILER INVOCATION
/home/shw2bk/usr/local/bin/m68k-elf-gcc -save-temps -c -g -Wall -O2 -m5407
-fno-strict-aliasing -o 2m_tpl.o 2m_tpl.c
# COMPILER OUTPUT
2m_tpl.c: In function `TB2M_Calculate_J1_CRC':
2m_tpl.c:84: error: insn does not satisfy its constraints:
(insn 255 202 130 5 (nil) (set (reg:QI 9 %a1)
(mem:QI (plus:SI (reg/f:SI 14 %a6)
(const_int -7 [0xfff9])) [0 J1_CRC_Byte S1 A8])) 37
{*m68k.md:1060} (nil)
(nil))
2m_tpl.c:84: internal compiler error: in reload_cse_simplify_operands, at
reload1.c:8353
Please submit a full bug report,
with preprocessed source if appropriate.
See URL:http://gcc.gnu.org/bugs.html for instructions.
2m_tpl.c
Description: Binary data
2m_tpl.i
Description: Binary data
[Bug c++/18201] New: Compiler suggests submitting a bug report after exiting while printing error message
The following should compile with an error message but the compiler dies in the middle of printing an error message #include string template class charT std::basic_ostream(charT) operator(std::basic_ostreamcharT os); -- Summary: Compiler suggests submitting a bug report after exiting while printing error message Product: gcc Version: 3.2 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: ron at vaniwaarden dot org CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18201
[Bug c++/18201] Compiler suggests submitting a bug report after exiting while printing error message
--- Additional Comments From pinskia at gcc dot gnu dot org 2004-10-28 16:30 --- Fixed since 3.2.2: pr18201.cc:4: error: invalid use of template-name 'std::basic_ostream' in a declarator pr18201.cc:4: error: syntax error before `' token pr18201.cc:4: error: `charT' was not declared in this scope pr18201.cc:4: error: template argument 1 is invalid pr18201.cc:4: error: template argument 2 is invalid pr18201.cc:4: warning: ISO C++ forbids declaration of `operator' with no type pr18201.cc:4: warning: ISO C++ forbids declaration of `os' with no type pr18201.cc:4: error: `int operator(int)' must have an argument of class or enumerated type pr18201.cc:4: error: `int operator(int)' must take exactly two arguments 3.4 gives: t.cc:4: error: expected constructor, destructor, or type conversion before token t.cc:4: error: expected `;' before token -- What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||FIXED Target Milestone|--- |3.1.x/3.2.x http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18201
[Bug c++/18203] New: Compiler suggests submitting a bug report after exiting while printing error message
The following should compile with an error message but the compiler dies in the middle of printing an error message #include string template class charT std::basic_ostream(charT) operator(std::basic_ostreamcharT os); -- Summary: Compiler suggests submitting a bug report after exiting while printing error message Product: gcc Version: 3.2 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: ron at vaniwaarden dot org CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18203
[Bug c++/18203] Compiler suggests submitting a bug report after exiting while printing error message
--- Additional Comments From ron at vaniwaarden dot org 2004-10-28 16:54 --- (In reply to comment #0) Problem does not occur with g++ 3.2.2 or 3.4.1 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18203
[Bug c++/18203] Compiler suggests submitting a bug report after exiting while printing error message
--- Additional Comments From pinskia at gcc dot gnu dot org 2004-10-28 16:56 --- If the problem only occurs in 3.2 and not in 3.2.2, the problem is already fixed. -- What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||FIXED Target Milestone|--- |3.3.2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18203
gfortran internal compiler error - Please submit a full bug report being attempted
Reporting the bug requires setting up my 1,070,045th user account
somewhere
so I will use the email version as the gccbug script exists somewhere
else.
Mac Os X 10.3.5
Dual 1.8 G5 Mac standard configuration, i.e middle model before first
speed bump
sudo fink install gfortran used to install
after fixing the fink configuration files to find gfortran under
unstable
and fighting with the stupid installation which did not like the Aqua
X11
which had never before required the SDK. Somebody's attempt at being
helpful
was a major PITA. Why would a command line compiler need X11? Either
they
think everyone else will want it, which is not he case. Or they require
some
piece of it as a utility, which is curious software engineering. Yes,
fink
isn't gfortran but it is rather hard to tell them apart while the
install
is in progress.
g5Mac:~/Cmd/gfortran gordon$ gfortran -v
Reading specs from /sw/lib/gcc/powerpc-apple-darwin7.5.0/3.5.0/specs
Configured with: ../gcc-3.5-20040815/configure --prefix=/sw
--enable-languages=f95 --infodir=/share/info --with-gmp=/sw
--disable-shared
Thread model: posix
gcc version 3.5.0 20040815 (experimental)
g5Mac:~/Cmd/gfortran gordon$ gfortran gfortran_bug.f90
gfortran_bug.f90: In function `initch':
gfortran_bug.f90:0: internal compiler error: in check_pointer_types_r,
at gimplify.c:4261
Please submit a full bug report,
with preprocessed source if appropriate.
See URL:http://gcc.gnu.org/bugs.html for instructions.
=
module typasc
implicit none
integer(kind=1)::asctab(256)
end module typasc
module typchr
implicit none
character(len=1)::chrtab(256)
end module typchr
module programs
implicit none
contains
subroutine main
implicit none
call initch
stop
end subroutine main
subroutine initch
use typchr
use typasc
implicit none
integer::i,ia,ic
character(len=1)::txblnk=
integer::asblnk=32
character(len=1)::text(95)=(/
,!,'',#,$,%,,',(,),*,+,,,-,.,/,0,1,2
,3,4,5,
6,7,8,9,:,;,,=,,?,@,A,B,C,D,E,F,G,
H,I,J,K,L,M,N,O,P,Q,R
,S,T,U,V,W,X,Y,Z,[,\,],^,_,`,a,b,c,d
,e,f,g,h,i,j,k,l,m,n,
o,p,q,r,s,t,u,v,w,x,y,z,{,|,},~/)
integer(kind=1)::ascii(95)=(/
32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,
56,57,58,59,60,
61,62,63,64,65,66,67,68,69,70,71,72,73,74,75,76,77,78,79,80,81,82,83,84,
85,86,87,88,89,90,91,92,93,94,95,96,97,98,
99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,1
17,118,119,120,121,122,123,124,125,126/)
do i=1,256
asctab(i)=asblnk
chrtab(i)=txblnk
end do
do i=1,95
ic=ascii(i)
chrtab(ic+1)=text(i)
ia=ichar(text(i))
asctab(ia+1)=ascii(i)
end do
return
end subroutine initch
end module programs
program acssuprs
use programs
implicit none
call main
end program acssuprs
=
Gordon Sande Sande Associates
(902) 443-252810 Regency Park Drive #604
[EMAIL PROTECTED] Halifax, Nova Scotia B3S 1P2
Re: gfortran internal compiler error - Please submit a full bug report being attempted
On Oct 20, 2004, at 9:21 AM, Gordon Sande wrote: Reporting the bug requires setting up my 1,070,045th user account somewhere so I will use the email version as the gccbug script exists somewhere else. Mac Os X 10.3.5 Dual 1.8 G5 Mac standard configuration, i.e middle model before first speed bump sudo fink install gfortran used to install Actually installing gfortran from source is not that hard on powerpc-darwin (I do it all the time). g5Mac:~/Cmd/gfortran gordon$ gfortran -v Reading specs from /sw/lib/gcc/powerpc-apple-darwin7.5.0/3.5.0/specs Configured with: ../gcc-3.5-20040815/configure --prefix=/sw --enable-languages=f95 --infodir=/share/info --with-gmp=/sw --disable-shared Thread model: posix gcc version 3.5.0 20040815 (experimental) This is already fixed in a later version of gfortran, 4.0.0 20041017. Please ask fink to update their gfortran. Thanks, Andrew Pinski
gfortran says to submit bug report
While attempting to compile the NIST FDS4 code (f90 based) I get the following error pcp05454784pcs:~/Codes/Fortran_Compiles/fds_test_compile jakoski$ make gfortran -c -O3 -ffixed-form mods.f mods.f:628: internal compiler error: backend decl for module variable y_f_inlet already exists Please submit a full bug report, with preprocessed source if appropriate. See URL:http://gcc.gnu.org/bugs.html for instructions. make: *** [mods.o] Error 1 No preprocessed source appeared when I added -save-temps to the compile line. The compiler info is pcp05454784pcs:~/Codes/Fortran_Compiles/fds_test_compile jakoski$ gfortran -v Reading specs from /usr/local/lib/gcc/powerpc-apple-darwin7.5.0/4.0.0/specs Configured with: ../gcc/configure --enable-threads=posix --enable-languages=f95 --enable-static --disable-shared Thread model: posix gcc version 4.0.0 20041009 (experimental) I'm running on a dual processor G5 Mac under OS X 10.3.5 with Xcode 1.5 installed. The source code and make file (for xlf Fortran) are available as downloads from http://fire.nist.gov/fds/ Hope this helps your efforts. Let me know if you need more info. Joe Koski [EMAIL PROTECTED]
Re: gfortran says to submit bug report
On Oct 11, 2004, at 12:38 PM, Joe Koski wrote: backend decl for module variable This is most likely the same as PR 17917. Thanks, Andrew Pinski
Re: gfortran says to submit bug report
Andrew, After reading 17917, I agree. Thanks for your reply. Joe Koski on 10/11/04 11:03 AM, Andrew Pinski at [EMAIL PROTECTED] wrote: On Oct 11, 2004, at 12:38 PM, Joe Koski wrote: backend decl for module variable This is most likely the same as PR 17917. Thanks, Andrew Pinski
