Displaying 20 results from an estimated 110 matches similar to: "How can I declare an empty zoo object?"
2006 May 12
2
How to declare several HABTM-relationships?
Hello,
Is it possible to have several HABTM-relationships for the same object?
Example: Imagine I have 3 objects (classroom, student, teacher) and
define the associations for the student as:
class Student < ActiveRecord::Base
has_and_belongs_to_many :classrooms
has_and_belongs_to_many :teachers
class Classroom < ActiveRecord::Base
has_and_belongs_to_many :students
class Teacher <
2006 Mar 02
0
Way to put javascript you want to appear in the head but declare it in a template?
I have some javascript that is specific to an rhtml template but must appear
in the <head></head> section. I figured I could just put it in a variable
at the top of my template and make my layout conditionally output that
variable if it existed. But is there a better way to do this that has
already been standardized in rails?
Thanks,
Carl
-------------- next part --------------
An
2006 Jan 26
3
Newbe:Where declare constants visible in view & controller ?
I am using some constants that should be visible in the controller and
in a view.
Declaring the constant in the controller does not make the constant
visible in the view.
So my question:
Where can I declare the constant to be visible in all views and
controllers ?
Thanks a lot in advance
Christian
--
Posted via http://www.ruby-forum.com/.
2017 Sep 19
0
Jump Threading duplicates dbg.declare intrinsics for fragments, bug?
On Tue, Sep 19, 2017 at 8:40 AM, Adrian Prantl via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> > Later loop unroll comes and unrolls the loop and then suddenly we have
> two absolutely identical dbg.declares and the assert in addFragmentOffset()
> blows. Who's at fault?
>
> Without having read the code yet, my intuition says that the unroller
> should not be
2017 Sep 20
1
Jump Threading duplicates dbg.declare intrinsics for fragments, bug?
On Wed, Sep 20, 2017 at 1:43 AM, Mikael Holmén <mikael.holmen at ericsson.com>
wrote:
> I also think it's weird that the replaceDbgDeclareForAlloca/rep
> laceDbgDeclare/FindAllocaDbgDeclare methods return as soon as they've
> handled one found dbg.declare, so if there are several, one is moved next
> to the alloca, but the other ones are left somewhere. So maybe a fault
2006 May 08
0
[patch] s390 syscall.c declare err
commit 54599b2bfd5e0c66d74c721f0a96acb4822a64d7 removed err declaration
usr/klibc/arch/s390/syscall.c: In function '__syscall_common':
usr/klibc/arch/s390/syscall.c:10: error: parameter name omitted
usr/klibc/arch/s390/syscall.c:12: error: 'err' undeclared (first use in this function)
Signed-off-by: maximilian attems <maks@sternwelten.at>
diff --git
2006 Sep 18
1
[LLVMdev] how to declare that two registers must be different
Rafael Espíndola wrote:
>> "The destination register shall not be the same as the operand
>> register Rm. R15 shall not be used as an operand or as the
>> destination register."
>
> The ARM ARM has this "Operand restriction" on MUL:
> Specifying the same register for <Rd> and <Rm> has UNPEDICTABLE results.
>
>>
2006 Sep 19
0
[LLVMdev] how to declare that two registers must be different
> My copy of the ARM ARM says:
>
> "Use of R15: Specifying R15 for register <Rd>, <Rm>, or <Rs> has
> UNPREDICTABLE results."
>
> This is the same as above. However, it goes on to say:
>
> "Operand restriction: Specifying the same register for <Rd> and <Rm> was
> previously described as producing UNPREDICTABLE results. There
2007 Nov 26
1
[LLVMdev] How to declare and use sprintf
Hello, Jon
> What is the correct way to do this?
FunctionType constructor takes extra boolean for marking a varargs
function.
There is some trick: feed your bytecode to llvm2cpp tool and you'll get
C++ source, which will construct the module you provided. From this
source you can see, how different things can be created via LLVM API.
--
With best regards, Anton Korobeynikov.
Faculty
2010 Jul 17
2
[LLVMdev] llvm.dbg.declare
Hi folk,
In the Source Level Debugging document, llvm.dbg.declare takes two
paramters. "The first argument is the alloca for the variable, cast to a
{}*. The second argument is the llvm.dbg.variable containing the description
of the variable." The second parameter corresponds to DIVariable, what is
the corresponding LLVM class of the first parameter? I want to find which
2010 Jul 19
0
[LLVMdev] llvm.dbg.declare
On Sat, Jul 17, 2010 at 12:00 AM, Neal N. Wang <neal.wang at gmail.com> wrote:
> Hi folk,
>
> In the Source Level Debugging document, llvm.dbg.declare takes two
> paramters. "The first argument is the alloca for the variable, cast to a
> {}*. The second argument is the llvm.dbg.variable containing the description
> of the variable." The second parameter
2011 Jan 06
0
[LLVMdev] Null address pointer in llvm.dbg.declare
Hi,
I'm encountering a problem with llvm.dbg.declare. My code looks
basically like this:
if(DbgDeclareInst *dbg = dyn_cast<DbgDeclareInst>(&inst)) {
const Value* addr = dbg->getAddress();
const MDNode* mvar = dbg->getVariable();
...
}
While the MDNode (mvar) contains the correct information (name of the
variable, etc...), getAddress always returns NULL. Am I
2012 Jul 18
0
[LLVMdev] Fix for forward-declare-class.cpp in debuginfo-tests
Hi,
I'm not sure where to post this since it relates to the "debuginfo-tests" repository, so please tell me where to forward it if this is the wrong place!
I've fixed the forward-declare-class.cpp test-case in the attached patch.
It seems that gdb has fixed their bug in version 7.4, so the patch uses a regex to match expected output for both the broken and fixed gdb.
Cheers
2012 Jul 23
1
[LLVMdev] Fw: Fix for forward-declare-class.cpp in debuginfo-tests
Hi,
Please could someone kindly review this patch for me?
Many thanks
Andy
On Wednesday, July 18, 2012 9:15 AM, Andy Gibbs wrote:
> Hi,
>
> I'm not sure where to post this since it relates to the "debuginfo-tests"
> repository, so please tell me where to forward it if this is the wrong
> place!
>
> I've fixed the forward-declare-class.cpp test-case in
2016 Dec 12
2
[RFC] Enable "#pragma omp declare simd" in the LoopVectorizer
)On 12 December 2016 at 13:44, Francesco Petrogalli
<Francesco.Petrogalli at arm.com> wrote:
> I am using “D” for 64-bit NEON and “Q” for 128-bit NEON, which makes NEON
> vector symbols look as follows:
>
> _ZVGQN2v__Z1fd
> _ZVGDN2v__Z1ff
> _ZVGQN4v__Z1ff
Hi Francesco,
The ARM AAPCS (A.2.1) says:
"For C++ the mangled name for parameters is as though the equivalent
2016 Dec 12
0
[RFC] Enable "#pragma omp declare simd" in the LoopVectorizer
On 12/12/2016 14:32, "Renato Golin" <renato.golin at linaro.org> wrote:
>Clang is already able to mangle NEON vectors of any length
>(CXXNameMangler::mangleNeonVectorType), you should use that, as this
>is very likely to be compatible with other compilers as well.
Hi Renato,
The “u”, “v”, “l” mangling of parameters has already been agreed
internally at ARM with the gcc
2005 Mar 07
0
Asterisk & Fritz & Capi & isdn PBX integration : Can I dial out on any MSN I declare ?
Hi,
I'm integrating Asterisk to legacy PBX via ISDN router. If I want to call
legacy PBX internal extension I need to specify MSN as caller id and local
number to call.
I wonder if I can cal out via Fritz & CAPI on any msn I want, or are there
any limitations - I've read something about 5 MSNs limitation and wonder if
it still holds ?
Thanks in advance,
regards,
Rob.
2005 Oct 31
1
MS Visual FoxPro DECLARE command doesnt work
I'm a programmer using Microsoft Visual FoxPro for daily work. I'm
trying to run a self written program on wine. This program uses several
Windows API functions. An example is:
DECLARE INTEGER ShellExecute IN z:/usr/lib/wine/shell32.dll.so ;
INTEGER, STRING, STRING, STRING, STRING, INTEGER
ShellExecute( 0, "open", "notepad.exe", "", "", 1 )
2019 Sep 25
0
[nbdkit PATCH 2/2] common/protocol: Declare additional constants
We aren't using them yet, but as we are now publishing this file, it's
worth letting other clients have a chance to use named bits reserved
by the protocol. This does not expose anything related to resize, as
that is still experimental.
Signed-off-by: Eric Blake <eblake@redhat.com>
---
common/protocol/nbd-protocol.h | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
2020 Jun 01
1
[v2v PATCH] libosinfo: declare OsinfoList auto-cleanup with glib < 2.63.3
Starting from glib 2.63.3, Module classes have already auto-cleanup
functions declared for them.
Reported by: Kevin Locke.
---
v2v/libosinfo-c.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/v2v/libosinfo-c.c b/v2v/libosinfo-c.c
index 1ab6bb4d..e6827f76 100644
--- a/v2v/libosinfo-c.c
+++ b/v2v/libosinfo-c.c
@@ -44,7 +44,9 @@
G_DEFINE_AUTOPTR_CLEANUP_FUNC(OsinfoFilter, g_object_unref)