[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Release
- To: petsc-dev@xxxxxxxxxxx
- Subject: Re: Release
- From: "Lisandro Dalcin" <dalcinl@xxxxxxxxx>
- Date: Tue, 25 Sep 2007 18:40:37 -0300
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=VEZAjbPKJbGHGygZP8xbXSUxTFgwk8zm8YDcTae5bzg=; b=b87mndhC9CT/simce4zWjHzM5Y0YkiQ99EitmApFlL/Thv791WGk386gE2jqXvmPTU5ZzqnAgOEdBzjQjaaKXG56rXx++QpNAlzduP14JGLyJLV5COG/9JhTnT9xbyjpkCiYjKQqfuTYYWSMeOGnNWWcyBqWmplkZ/iUT+4Ne0U=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=GdZasEHJH/wRu3P/uhsz1fK1bzj/XZpWxjrT2ckYbMayHBx0TcpvQ0ugdxdXtDdMR1DtfdEqlsiQAJ9vYL39QNBm1Kza0n0l0Lpj/kajiqbfCVwynOzeSuHli/rU/WqGIAtjhlzalqztgudpFMDbfaF6dI8Ss66ZFkIejbpZ6LI=
- In-reply-to: <a9f269830709221122v782b9897n8c3de0d21515d423@mail.gmail.com>
- References: <a9f269830709221122v782b9897n8c3de0d21515d423@mail.gmail.com>
- Reply-to: petsc-dev@xxxxxxxxxxx
- Sender: owner-petsc-dev@xxxxxxxxxxx
On 9/22/07, Matthew Knepley <knepley@xxxxxxxxx> wrote:
> What do you think about 2.4 in October? I really want to get the new
> install out there.'
I'm experimenting at home about a way to compile petsc with
'-fstrict-aliasing', in order to follow C99 strict aliasing rules.
However, If I am right, this requiered a new layout for PetscObect's
structure (I basically followed the approach being used for Python
3.0). As a side effect, some very commonly used struct members (like
'comm', 'type_name', and 'prefix') have to be accessed by casting
derived objecs as PetscObject, i.e.: Vec v; ((PetscObject)v)->comm.
I have also some problems when calling PetscObjectQueryFunction, as
the compiler complains about strict aliasing rules, and I need to
define an additional function pointer, get the function, and next cast
to the a actual func. pointer to do the call. Not suure yet if this
can be improved, perhaps a macro can help.
Is there any interest in this be completed? It's a nonsense? In case
you want me to continue this work, I will need a bit of help in a few
places related to low-level calls related to sockets and sys calls.
--
Lisandro Dalcín
---------------
Centro Internacional de Métodos Computacionales en Ingeniería (CIMEC)
Instituto de Desarrollo Tecnológico para la Industria Química (INTEC)
Consejo Nacional de Investigaciones Científicas y Técnicas (CONICET)
PTLC - Güemes 3450, (3000) Santa Fe, Argentina
Tel/Fax: +54-(0)342-451.1594