[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #48531] LTO warnings in liboctave
From: |
Mike Miller |
Subject: |
[Octave-bug-tracker] [bug #48531] LTO warnings in liboctave |
Date: |
Sun, 17 Jul 2016 03:43:57 +0000 (UTC) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:47.0) Gecko/20100101 Firefox/47.0 |
Follow-up Comment #3, bug #48531 (project octave):
Ok, I do see these warnings with GCC 6 but not 5.
I guess this may be due to or a side effect of some GCC 6 changes related to:
> Type merging was fixed to handle C and Fortran interoperability
> rules as defined by the Fortran 2008 language standard.
from https://gcc.gnu.org/gcc-6/changes.html.
I don't see what you're saying about the existing code assuming that a
std::complex<float> can be converted to a C float complex type. Does putting a
function signature in an extern "C" block somehow allow the compiler to treat
a std::complex<T> argument as a C complex argument? The existing code is
written to ensure that the C++ code passes a pointer to a std::complex<T>
array, and the Fortran code is expecing a Fortran complex array. The C++
signature could be written with a void* parameter type instead and it would
still work as well.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?48531>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #48531] LTO warnings in liboctave, Robert Jenssen, 2016/07/16
- [Octave-bug-tracker] [bug #48531] LTO warnings in liboctave, Mike Miller, 2016/07/16
- Message not available
- [Octave-bug-tracker] [bug #48531] LTO warnings in liboctave,
Mike Miller <=
- Message not available
- [Octave-bug-tracker] [bug #48531] LTO warnings in liboctave, John W. Eaton, 2016/07/17
- [Octave-bug-tracker] [bug #48531] LTO warnings in liboctave, John W. Eaton, 2016/07/18
- [Octave-bug-tracker] [bug #48531] LTO warnings in liboctave, John W. Eaton, 2016/07/18
- [Octave-bug-tracker] [bug #48531] LTO warnings in liboctave, Robert Jenssen, 2016/07/18
- [Octave-bug-tracker] [bug #48531] LTO warnings in liboctave, John W. Eaton, 2016/07/18
- [Octave-bug-tracker] [bug #48531] LTO warnings in liboctave, Mike Miller, 2016/07/18
- [Octave-bug-tracker] [bug #48531] LTO warnings in liboctave, John W. Eaton, 2016/07/18