On 2013-10-25 00:06+0100 Andrew Ross wrote:
> I've tried a compile with the full list of warning flags in the README.release
> file, plus -Wuninitialized. This shows loads of swig errors. Most of these are
> in swig code, but I've mangaged to squash a few in the .i files. I've not yet
> tackled th
On 2013-10-21 21:36-0700 Alan W. Irwin wrote:
> I can only reproduce these valgrind issues for example 16 if a certain
> amount (-O2 or -O3) of optimization is turned on. Here are the
> valgrind warnings for the -g -O2 case (which were identical to these
> same 10 warnings for the -g -O3 case, bu
On Thursday 24 Oct 2013 13:24:43 Alan W. Irwin wrote:
> On 2013-10-24 12:12-0700 Alan W. Irwin wrote:
> > I hope you will continue this process dealing with the -O3
> > -Wuninitialized warnings for our swig-generated code, and I plan to do
> > the same for the rest of our code.
>
> Hi Andrew:
>
>
On 2013-10-24 12:12-0700 Alan W. Irwin wrote:
> I hope you will continue this process dealing with the -O3
> -Wuninitialized warnings for our swig-generated code, and I plan to do
> the same for the rest of our code.
Hi Andrew:
I just discovered for the test_noninteractive and install targets we
On 2013-10-21 21:36-0700 Alan W. Irwin wrote:
> Tomorrow (Tuesday) I plan to move on to working on the uninitialized
> variables in the code in the src subdirectory that are revealed by -O3
> -Wuninitialized to help work toward the overall goal of getting rid of
> all these warnings throughout our
On 2013-10-21 19:07-0700 Alan W. Irwin wrote:
> When I tried that on my 64-bit Linux system I discovered plcolorbar
> memory management issues which I am planning to look at this evening.
> So with luck I should be able to achieve valgrind perfect results for
> all our examples in the 64-bit case.
On 2013-10-21 22:11+0100 Andrew Ross wrote:
>
> Alan,
>
> [... T]he rounding issues are not an intrinsic 32-bit issue. With a 32-bit
> version of Debian unstable (running under pbuilder) I get completely clean
> results for make test_diff_psc, with the exception of stdout for the python
> example
On 2013-10-21 22:34+0100 Andrew Ross wrote:
>
> I now understand why the code is different. The typemap for mapform_func
> mapform has a default clause which controls what happens if the argument is
> omitted. It seems that once swig has encountered an optional argument all
> subsequent arguments
I now understand why the code is different. The typemap for mapform_func
mapform has a default clause which controls what happens if the argument is
omitted. It seems that once swig has encountered an optional argument all
subsequent arguments are also counted as optional so are wrapped with an
Alan,
Firstly, the rounding issues are not an intrinsic 32-bit issue. With a 32-bit
version of Debian unstable (running under pbuilder) I get completely clean
results for make test_diff_psc, with the exception of stdout for the python
example 23. This is with python 2.7.5.
Compiling plplotcmo
Hi Andrew:
We need further followups from you when you can find the time.
More details below in context.
On 2013-10-19 22:09-0700 Alan W. Irwin wrote:
> On 2013-10-19 12:53-0700 Alan W. Irwin wrote:
>
>> Well, there are 74 such instances [in the make.out generated by
> MSVC].
>
> It turned
On 2013-10-19 12:53-0700 Alan W. Irwin wrote:
> Well, there are 74 such instances [in the make.out generated by
MSVC].
It turned out that -O0 -Wuninitialized picked up those 74 issues as
well (on Linux). So I fixed those (revision 12611). None of those
were false alarms, but they all concern
On 2013-10-19 18:48- Arjen Markus wrote:
> HI Alan,
>
> from a first glance, I think they are false alarms - they show up in clean-up
> code. But
> that is only a preliminary conclusion from just a glance.
Hi Arjen:
Well, there are 74 such instances. I agree the first one for tmp8
seems to
files.
Regards,
Arjen
> -Original Message-
> From: Alan W. Irwin [mailto:[email protected]]
> Sent: Saturday, October 19, 2013 8:43 PM
> To: Arjen Markus
> Cc: PLplot development list; Andrew Ross
> Subject: RE: [Plplot-devel] Problem builiding the Python b
Hi Alan,
> -Original Message-
> From: Arjen Markus [mailto:[email protected]]
...
> (There is also the Java issue for this platform.)
Well, that is solved too: just a few small corrections to the wrapper code and
some juggling with the PATH variable that
were required on my machin
On 2013-10-19 17:22- Arjen Markus wrote:
> The compiler warnings do not seem to be of much interest - I have attached
> the full output of nmake,
> but I do not see anything that could help us with this rounding problem.
On the contrary, I think these results might be more interesting than
i
The compiler warnings do not seem to be of much interest - I have attached the
full output of nmake,
but I do not see anything that could help us with this rounding problem.
Regards,
Arjen
> -Original Message-
> From: Arjen Markus [mailto:[email protected]]
...
>
> I did notice
Hi Alan,
> -Original Message-
> From: Alan W. Irwin [mailto:[email protected]]
> Sent: Saturday, October 19, 2013 6:50 PM
> To: Arjen Markus
> Cc: PLplot development list; Andrew Ross
> Subject: RE: [Plplot-devel] Problem builiding the Python bindings on Window
Hi Alan, Andrew,
> -Original Message-
> From: Arjen Markus [mailto:[email protected]]
>
> - The ones that do not simply crash at some point. These are: 08, 09, 11, 15,
> 16, 20,
> 21 and 22.
> I have not looked into the possible cause of this. It may be a single
> function that
Hi Arjen:
Thanks very much for running the Python-C comparisons for both
MinGW/MSYS (and later) MSVC on 32-bit Windows. More below in context.
On 2013-10-19 14:08- Arjen Markus wrote:
>> From: Alan W. Irwin [mailto:[email protected]]
>> So the next step in trying to figure out the c
> Cc: PLplot development list; Andrew Ross
> Subject: Re: [Plplot-devel] Problem builiding the Python bindings on Windows
> using
> MS VC/C++
>
> Hi Alan,
>
> > -Original Message-
> > From: Alan W. Irwin [mailto:[email protected]]
> > I did in
Hi Alan,
> -Original Message-
> From: Alan W. Irwin [mailto:[email protected]]
>
> python
>Missing examples:
>Differing postscript output : 00 03 04 05 06 08 09 11 12 14 14a 15 16 17
> 18 19 20
> 21 22 23 25 26 27 29 33
>Missing stdout :
>
Hi Alan,
> -Original Message-
> From: Alan W. Irwin [mailto:[email protected]]
> I did install python-2.7.5 and numpy-1.7.1, and immediately encountered the
> PyArray_FLOAT build errors Arjen encountered. I created a proper fix for
> those as of
> revision 12606. That allowed me
On 2013-10-18 09:30-0700 Alan W. Irwin wrote:
> On 2013-10-18 01:03-0700 Alan W. Irwin wrote:
>
>> On 2013-10-18 07:07- Arjen Markus wrote:
>>> I removed the #define NPY_NO_DEPRECATED_API ... line from
>> plplotcmodule.i, even though this has been in there for a long time,
>> and that helped a
On 2013-10-18 01:03-0700 Alan W. Irwin wrote:
> On 2013-10-18 07:07- Arjen Markus wrote:
>> I removed the #define NPY_NO_DEPRECATED_API ... line from
> plplotcmodule.i, even though this has been in there for a long time,
> and that helped a bit: the complaints about PyArray_FLOAT are gone.
>
>
On 2013-10-18 07:07- Arjen Markus wrote:
> [...]As I am trying to build it on bare Windows, that macro is not defined
> and so I get into the #else
> branch. [...]
Sorry, Arjen. I missed before that you were doing a build with bare
Windows. I assume in the rest of this that means you having
Hi Alan,
(changed the subject to better reflect the content)
The problems I had before with building the Python bindings had to do with
MinGW and
the location of the Numpy package. The current problems are however of a very
different
nature.
I removed the #define NPY_NO_DEPRECATED_API ... line
27 matches
Mail list logo
