Skip to content

R
riscv-gcc-1
Switch branch/tag
  1. 15 Sep, 2015 33 commits
  3. 14 Sep, 2015 7 commits
    • [PATCH] Minor DOM cleanup · 55133eae 
              PR tree-optimization/47679
	* tree-ssa-dom.c (avail_expr_hash): Pass a pointer to a real
	type rather than void *.

From-SVN: r227762
      Jeff Law committed
    • re PR c++/44282 (fastcall is not mangled at all) · 65440c48 
      	PR c++/44282

	* mangle.c (write_CV_qualifiers_for_type): Also warn about regparm
	mangling with lower -fabi-version.

From-SVN: r227761
      Jason Merrill committed
    • The flag diagnostic_context::some_warnings_are_errors controls whether to give... · 0d179691 
      The flag diagnostic_context::some_warnings_are_errors controls whether
to give the message "all warnings being treated as errors". However, when
warnings are buffered and then discarded, this flag is not reset. It turns
out we do not need this flag at all, since we already count explicitly how
many warnings were converted into errors, and this number is kept up to
date for the buffered diagnostics used by Fortran.

gcc/ChangeLog:

2015-09-14  Manuel López-Ibáñez  <manu@gcc.gnu.org>

	PR fortran/67460
	* diagnostic.c (diagnostic_initialize): Do not set
	some_warnings_are_errors.
	(diagnostic_finish): Use DK_WERROR count instead.
	(diagnostic_report_diagnostic): Do not set
	some_warnings_are_errors.
	* diagnostic.h (struct diagnostic_context): Remove
	some_warnings_are_errors.

gcc/testsuite/ChangeLog:

2015-09-14  Manuel López-Ibáñez  <manu@gcc.gnu.org>

	PR fortran/67460
	* gfortran.dg/pr67460.f90: New test.

From-SVN: r227760
      Manuel López-Ibáñez committed
    • compiler: Ignore result context in constant expressions. · 34e98513 
          
    When evaluating a constant expression, the gofrontend would incorrectly
    force each operand to be represented as the resulting type before
    checking if the operation was valid with the untyped constants.
    According to the language specification on constant
    expressions(http://golang.org/ref/spec#Constant_expressions): "Untyped
    boolean, numeric, and string constants may be used as operands wherever
    it is legal to use an operand of boolean, numeric, or string type,
    respectively."
    
    Fixes golang/go#11566.
    
    Reviewed-on: https://go-review.googlesource.com/12716

From-SVN: r227758
      Ian Lance Taylor committed
    • [SPARC] Simplify const_all_ones_operand · 5c270a92 
      gen_rtx_CONST_VECTOR ensures that there is a single instance of:

       (const_vector:M [(const_int -1) ... (const_int -1)])

for each M, so pointer equality with CONSTM1_RTX is enough.  Also,
HOST_BITS_PER_WIDE_INT == 32 is doubly dead: HOST_WIDE_INT is always
64 bits now, and we always use const_int rather than const_double
or const_wide_int for all-ones values (or any other value that
fits in a signed HOST_WIDE_INT).

gcc/
	* config/sparc/predicates.md (const_all_ones_operand): Use
	CONSTM1_RTX to simplify definition.

From-SVN: r227757
      Richard Sandiford committed
    • ChangeLog: Fix shitespace. · 81fc3217 
      	* ChangeLog: Fix shitespace.
	* testsuite/ChangeLog: Ditto.

From-SVN: r227756
      Uros Bizjak committed
    • dump-new-function-3.c (dg-final): Also scan for $loopfn. · b4e240a1 
      	* gcc.dg/gomp/dump-new-function-3.c (dg-final): Also scan for $loopfn.
	* gcc.dg/gomp/notify-new-function-3.c (dg-final): Ditto.

From-SVN: r227755
      Uros Bizjak committed