PR# 16174 Add C compiler flag to suppress "statement not reached" warnings

Problem Report Summary
Submitter: prestoat2000
Category: Runtime
Priority: Low
Date: 2009/08/21
Class: Feature Request
Severity: Non-critical
Number: 16174
Release: 6.3.76070
Confidential: No
Status: Analyzed
Responsible:
Environment: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.9.1.2) Gecko/20090803 Firefox/3.5.2 Solaris 10 on SPARC
Synopsis: Add C compiler flag to suppress "statement not reached" warnings

Description
On Solaris SPARC and x86 (32-bit and 64-bit), could you add the following
to CFLAGS in config.sh:

   -erroff=E_STATEMENT_NOT_REACHED

This turns off "statement not reached" warnings from the C compiler.  In my
experience, these are always benign and are due to code generated for
rescue clauses.

Of course, I can add this myself after I get a release, but it is one less
modification for me to make if you do it.
To Reproduce

										

									

								

							

						

					

				

			

		

	









	

		

			
Problem Report Interactions

			

				

					
					

						

							
							

								

									
									
										

											

									
											From:prestoat2000   
											Date:2009/08/21   
											
											Download   
										

										

                                            
											
										 	
Then it seems that the solution is to provide a distinct set of C compiler
flags to be used when compiling the runtime, but this might involve changes
to your build infrastructure since some code would have to know which
set of C compiler flags to use.



											
											
											

											
										

									

								

							

							
							

								

									
									
										

											

									
											From:manus_eiffel   
											Date:2009/08/21   
																							Status: Analyzed   
											
											Download   
										

										

                                            
											
										 	
I'm afraid of removing those warnings since they are sometime useful as the flags would impact both the generated C code and the runtime C compilation. I wish that they only raise the warning when it is really a problematic case.